You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I faced the above error when using self-hosted Linux Docker Runner,
I had tried to update the docker image and yet the system showed image up-to-date.
Can you try updating the image now by running
docker image pull docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-runner:1
If you ecnounter the following error
docker: Error response from daemon: docker: Error response from daemon: Conflict. The container name "/runner-76b247e7-b925-5e7b-9da2-1cda14c4ff2c" is already in use by container "c3403236e3af5962ed3a9b8771561bd2021974941cc8a89a40c6c66cecb18f53". You have to remove (or rename) that container to be able to reuse that name. See 'docker run --help'.
then remove the runner first with the following command and then try to update again
docker container rm -f runner-76b247e7-b925-5e7b-9da2-1cda14c4ff2c
The issue should be resolved now. Please feel free to let me know how it goes.
This only applies to self-hosted runners, in which case you would need access to the server on which you installed the runner. You would then run the docker command in a bash terminal.
If you use the normal Bitbucket cloud runners, you do not have to worry about outdated runners.
If you are using a self-hosted runner, the Docker command that starts the runner is provided to the user that creates the runner from our website, during the runner creation. It is not possible to retrieve this Docker command later.
If you did not create the runner yourself, you can ask the admin who created the runner if they have saved somewhere that command. If not, an admin needs to remove the existing runner from our website and create a new one; they will be given a Docker command to start the new runner. It would be good to save that command, in order to restart the runner after an update.