Pipeline runner unregistered when run as k8s job
Asked by Roman Verchikov:

Hello experts,

I'm trying to run bitbucket pipeline runner on my laptop as kubernetes job as described in [runners FAQ](https://support.atlassian.com/bitbucket-cloud/docs/pipelines-runners-frequently-asked-questions/#How-do-I-setup-Pipelines-Runner-with-Kubernetes) (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!


Answers:
author: Roman Verchikov
body: My mistake. Missed REPOSITORY_UUID in k8s Job definition. ????


Tags: bitbucket-cloud

bitbucket-runners

cloud