Describe the bug
Using latest tags in docker-compose can cause unwanted upgrades if using docker compose pull instead of make pull (which pulls the correct image and tag them as latest). This may accidentally pull incompatible versions and break a working deployment unexpectedly. This is especially risky for users running older or stable releases (for example, 24.11), because pulling will download newer images (e.g., 25.10.1) without warning.
Steps To Reproduce
- Deploy using docker-compose for a specific release (e.g., 24.11)
- Run
docker compose pull
- Docker downloads images tagged as
latest (typically the newest release)
- Deployment may break due to incompatibility or unexpected updates
Expected behavior
Images should always match the intended release version in the compose file, avoiding accidental upgrades or mismatches regardless of command usage.
Screenshots
N/A
System Informatioon:
- OS: Any
- Docker version: Any
- Browser and Browser Version (if applicable): N/A
- Additional context: The workflow currently relies on
make pull to determine and overwrite the tags as latest, but this is not a reliable safeguard against accidental upgrades.
Describe the bug
Using
latesttags in docker-compose can cause unwanted upgrades if usingdocker compose pullinstead ofmake pull(which pulls the correct image and tag them as latest). This may accidentally pull incompatible versions and break a working deployment unexpectedly. This is especially risky for users running older or stable releases (for example, 24.11), because pulling will download newer images (e.g., 25.10.1) without warning.Steps To Reproduce
docker compose pulllatest(typically the newest release)Expected behavior
Images should always match the intended release version in the compose file, avoiding accidental upgrades or mismatches regardless of command usage.
Screenshots
N/A
System Informatioon:
make pullto determine and overwrite the tags aslatest, but this is not a reliable safeguard against accidental upgrades.