Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,559,386
Community Members
 
Community Events
184
Community Groups

Pipeline runner unregistered when run as k8s job

Edited

Hello experts,

I'm trying to run bitbucket pipeline runner on my laptop as kubernetes job as described in runners FAQ (I use standard single-node deployment provided with Docker Desktop for Mac).

The runner is executed successfully, and I can see these lines in k8s logs which get updated every 30 seconds:

+ ./entrypoint.sh
[2022-09-27 22:56:15,918] Runner version: 1.364
[2022-09-27 22:56:15,949] Runner runtime: linux-docker
[2022-09-27 22:56:19,846] Copying Docker cli to working directory.
[2022-09-27 22:56:20,513] Starting websocket listening to RUNNER_UPDATED events.
[2022-09-27 22:56:20,729] Updating runner status to "ONLINE" and checking for new steps assigned to the runner after 0 seconds and then every 30 seconds.
[2022-09-27 22:56:21,447] Updating runner state to "ONLINE".
[2022-09-27 22:56:53,029] Updating runner status to "ONLINE" and checking for new steps assigned to the runner after 0 seconds and then every 30 seconds.
[2022-09-27 22:56:53,033] Updating runner state to "ONLINE".
[2022-09-27 22:57:24,441] Updating runner status to "ONLINE" and checking for new steps assigned to the runner after 0 seconds and then every 30 seconds.
[2022-09-27 22:57:24,445] Updating runner state to "ONLINE".
[2022-09-27 22:57:55,210] Updating runner status to "ONLINE" and checking for new steps assigned to the runner after 0 seconds and then every 30 seconds.
[2022-09-27 22:57:55,213] Updating runner state to "ONLINE".

However, when I navigate to the repository this runner is set up for (repo settings -> pipelines -> runners), the runner appears to be in UNREGISTERED state.

How do I troubleshoot what the problem is?

When I run the `docker run` command generated by bitbucket during registration of new runner on my laptop, everything works fine and runner appears in ONLINE state. This is the output from `docker run` command generated by bitbucket (note the absence of "... and checking for new steps assigned..." logs):

```
Status: Downloaded newer image for docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-runner:1
+ ./entrypoint.sh
[2022-09-26 18:47:02,243] Runner version: 1.364
[2022-09-26 18:47:02,279] Runner runtime: linux-docker
[2022-09-26 18:47:05,557] Copying Docker cli to working directory.
[2022-09-26 18:47:09,912] Starting websocket listening to RUNNER_UPDATED events.
[2022-09-26 18:47:10,128] Updating runner status to "ONLINE" and checking for new steps assigned to the runner after 0 seconds and then every 30 seconds.
[2022-09-26 18:47:10,584] Updating runner state to "ONLINE".
[2022-09-26 18:47:40,099] Updating runner state to "ONLINE".
[2022-09-26 18:48:10,098] Updating runner state to "ONLINE".
[2022-09-26 18:48:40,099] Updating runner state to "ONLINE".
[2022-09-26 18:49:10,099] Updating runner state to "ONLINE".
[2022-09-26 18:49:40,098] Updating runner state to "ONLINE".
[2022-09-26 18:50:10,099] Updating runner state to "ONLINE".
[2022-09-26 18:50:40,097] Updating runner state to "ONLINE".
[2022-09-26 18:51:10,099] Updating runner state to "ONLINE".
```

Thank you!

1 answer

1 accepted

2 votes
Answer accepted

My mistake. Missed REPOSITORY_UUID in k8s Job definition. 🤦‍♂️

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events