Thanks for the quick response @sam . I will try that.
Quick question. The “git pull” I am assuming pulls the latest version of discourse-docker right?
In general, is it necessary to upgrade discourse-docker and discourse at the same time?
Currently, I don’t have discourse-docker controlled by git. Instead, I download a specific revision of discourse-docker (as a Zip) when configuring the server and pin the version of discourse to a specific commit during deployment of discourse.
The reason I do this is in order to try and make the build repeatable ie. running the same command with the same configuration + source at 2 different times should produce the same artifact. In general this is a good idea and has got me out of loads of ops nightmares with other software over the years 
This is because it gives you the ability to roll back to a known good configuration.
However, I think I’m swimming against the tide here with discourse because it seems to want to pull the latest versions of various bits of software during the build. I’m starting to wonder if my attempts to make the build repeatable are actually shooting myself in the foot?