How do I force a "docker pull" before my build?

[Daniel Martin]

I have a build that is defined with one stage, one job, and that job is configured to use docker. I'm not building a docker image with this job; I'm conducting my entire build inside a docker image.

However, it seems that the build agents have different versions of the docker image I use to build with on them, meaning that I get slightly different results in my build depending on which build agent my build lands on.

I can't add a task to my existing job to execute `docker pull` of the appropriate image, because my entire job is set to be run inside a docker container.

I can't add a new job that does the `docker pull` command because that will then run on a different build agent.

My workaround at the moment is to always push my docker images with a unique tag based on the date and then modify the bamboo job configuration each time I push the docker image, but this seems highly suboptimal. Ideally, I would never touch the bamboo configuration.

[roman_baeriswyl]

I think at the bottom there is an optional field for:

Extra arguments for the docker run command

I have added:

--pull=always

there and it seems to work.