self hosted Docker image- Miss matching runner

Nalini Kumar

Hello,

 

I am new to new to this. We have Linux box with self hosted docker container registry along with bitbucket.

 

Getting below error when running bitbucket pipeline. 

 

<span>Runner matching labels:</span>

- linux

- self.hosted

<span>Runner name: xyzzyc</span>

Runner labels: self.hosted, linux

Runner version:

7

<span>current: 1.274</span>

8

<span>latest: 1.476</span>

<span>The version of this runner is outdated. Upgrade to the latest version (1.476). </span>

12

13

Build teardown<1s

1

<span>Searching for files matching artifact pattern artifact_store_paths</span>

2

3

<span>Searching for files matching artifact pattern environment_name</span>

4

5

<span>Searching for files matching artifact pattern environment_node</span>

6

7

<span>Searching for files matching artifact pattern **_output_**.xml</span>

8

9

<span>Searching for test report files in directories named [test-reports, TestResults, test-results, surefire-reports, failsafe-reports] down to a depth of 4</span>

10

<span>Finished scanning for test reports. Found 0 test report files.</span>

11

<span>Merged test suites, total number tests is 0, with 0 failures and 0 errors.</span>

12

13

Patrik S

Hello @Nalini Kumar and thank you for reaching out to Community!

The error shown in the logs is because the runner's image you have locally is outdated, and a newer version is available to be downloaded. In this case, to update the runner's image you can run the following command on your machine : 

docker image pull docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-runner:1

This should update it to the latest version available currently. 

After updating it, in order for the change to take effect, you will need to delete the current runner container and start it again. The below command can be used to remove a runner's container : 

docker container rm -f runner-<UUID>

where you need to replace the UUID with your runner's name.

After removing the container, you can start the runner again using the command you were given when you created the runner. In case you don't have that command saved, you can create a new runner in the UI and it will provide you with a fresh pre-configured docker command.

Let me know in case you have any questions.

Thank you, @Nalini Kumar !

Patrik S