We use our gitlab-ci to build fresh images with the latest version of our code.
These images are day to day built with the latest tag.
We tag images during the release process.
My problem is related to the latest tag.
We deploy automatically these images on servers to test our product.
However, on a test server if we pull the latest docker image (verified by its checksum), stop the compose and up it again, we sometime still have the content of the old image (for example a configuration file).
We tried with docker-compose up -d --force-recreate but it doesn't help.
The only way to fix it was:
docker-compose down
docker system prune -f
docker rmi $(docker images -q)
docker-compose pull
docker-compose up -d
Any better idea ?
According to the documentation, you can ignore data from previous volume with this:
docker-compose up -d --force-recreate --renew-anon-volumes