Nope, standard docker behavior - it pulls only if it doesn't have any image for it or if you specified a non-existing tag...
Since the docker-compose.yml always points to the latest tag and not to a specific version tag (easier maintenance and uniformity), you have to pull if you're running in a machine that previously downloaded an image from this repo
I manually deleted the allegroai/trains:latest image, that didn't help either
a machine that had previous installation, but I deleted the /opt/trains directory beforehand
Did you install on a new machine or on a machine that previously had Trains Server installed?
The reference in the docker-compose.yml is for allegroai/trains:latest
Hi WackyRabbit7 ,
I'm not sure I follow - you have 0.15.1, and the UI suggests you upgrade to 0.161 - this is the expected behavior...
Why would I have 0.15.1 if I followed the instructions of the docs?
not manually I assume that if I deleted the image, and then docker-composed up, and I can see the pull working it should pull the correct one
but shouldn't the :lastest make it redownload the right image?
my bad, I didn't look at the upgrade section
This is why in the upgrade section we explicitly request you do:docker-compose -f /opt/trains/docker-compose.yml pull
When I said not the expected behavior, I meant that following the instructions on the docs, should lead to downloading the latest version
sudo curl https://raw.githubusercontent.com/allegroai/trains-server/master/docker-compose.yml -o /opt/trains/docker-compose.yml
The instructions specify you should curl the latest docker-compose, which contains a reference to allegroai/trains:latest - currently, this image in docker hub is for Trains Server 0.16.1
Wait, suddenly the UI changed to 0.16.1, seems like I was shown a cached page
Yes, but docker already has the image cached...
Don't assume 🙂 - just try to issue the command
let me try to docker-compose down --rmi all