Summary

As per the documentation https://hub.docker.com/r/atlassian/bamboo-agent-base, there are some discrepancies, as explained below. 

• Named volume is created with the name bambooAgentVolume. But the run command points to bambooVolume instead of bambooAgentVolume. This might enable the agent to override some of the Bamboo Server files

  docker volume create --name bambooAgentVolume

• /var/atlassian/application-data/bamboo is passed as the mount volume. But it has to be mounted as /var/atlassian/application-data/bambo-agent. Because of this, the agent's data in the home directory might not persist

  docker run -e BAMBOO_SERVER=http://bamboo.mycompany.com/agentServer/ -v bambooVolume:/var/atlassian/application-data/bamboo --name="bambooAgent" --hostname="bambooAgent" -d atlassian/bamboo-agent-base

• BAMBOO_HOME can be changed to BAMBOO_AGENT_HOME to avoid confusion with Bamboo Server Home as per https://hub.docker.com/r/atlassian/bamboo

  For the BAMBOO_HOME directory that is used to store the repository data (amongst other things) we recommend mounting a host directory as a data volume⁠, or via a named volume.

Workaround:

Mount the Bambo Agents Home as /var/atlassian/application-data/bambo-agent instead of {{/var/atlassian/application-data/bamboo }}