Using latest in a docker-compose.yaml means your containers will always pull and run the most recent image available, which can introduce unexpected changes, break your application, or cause compatibility issues without warning. You lose control over exactly which version is deployed, making debugging harder and increasing the risk of untested updates being pushed to production. From a security standpoint, it’s also risky because you might not be aware of what’s actually running, and it becomes difficult to track vulnerabilities or reproduce environments reliably. Pinning to a specific tag ensures consistency, stability, and predictability across deployments.
If you want to be kept updated about the tags, you can check our dedicated page