Bamboo not able to run scheduled builds on Docker image/network
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Bamboo is unable to run scheduled jobs post trying to create a Docker network as one of the task, it errored out with a message "response from daemon: network with name m2mhubit_net already exist"
Here Docker container name is m2mhubit_net
Environment
Issue seen on 8.1.5
Diagnosis
Bamboo builds failed with below error
“docker: Error response from daemon: Conflict. The container name "/m2mhubit_redis" is already in use by container“Cause
Possible cause for this error was that the build plan was trying to create a Docker network that already exists.
Solution
To resolve this problem follow the below steps
Add a script that will stop and remove the Docker container before starting a new one.
docker stop m2mhubit_redis || true && docker rm m2mhubit_redis || trueHere m2mhubit_redis is the Docker container name
- Along with this enable Force Clean Build option in the “Source Code Checkout“ task.