Summary

The Configuring the Docker task in Bamboo documentation, under the "Run a Docker container" section, explains the functionality of the "Detached" option, but only for Deployment Projects.

By default, the container is removed on completion of the task, but you can select Detach container to have the container continue to run after a deployment project completes. Containers can be linked to detached containers started by preceding tasks in a job by selecting the Link to detached containers option.

This option, however, if also available for Build Plans, but the way it works is different. If "Detached" is not checked, the container gets deleted as soon as its task finishes. If selected, the container keeps running in the background throughout the next tasks of the same job, but it's still deleted once the respective build job finishes. This can lead to confusion, since "Detached" in docker means it will keep running in the background and won't be deleted, but Bamboo actually does delete it after the job completion.

Suggestion

Add more details to the aforementioned paragraph, explaining how it works for build plans. It also might be useful to let the customers know that we can actually force Bamboo to keep the containers running – please see this new KB: How to avoid Docker container deletion after build completion

I've also raised BAM-21757 to add this information to the Bamboo User Interface.