5 ms·
I always thought `:latest` was a bit of a special case. Ex: Pushing `2.0.1` followed by `1.1.4` would leave `1.1.4` as the `latest` image which could be an iss
by donmcronald 6y ago
I always thought `:latest` was a bit of a special case. Ex: Pushing `2.0.1` followed by `1.1.4` would leave `1.1.4` as the `latest` image which could be an issue by itself. Is that wrong?
I've always tried to pick stable tags [1] if they're available.
1. https://docs.microsoft.com/en-us/archive/blogs/stevelasker/docker-tagging-best-practices-for-tagging-and-versioning-docker-images#stable-tags https://docs.microsoft.com/en-us/archive/blogs/stevelasker/d...
- sfoley 6y agoThere is absolutely nothing special about `latest`, it’s just a tag like any other. It simply happens to be the default tag when omitted, just like how `origin` is the default remote name when performing a `git clone`.
- GauntletWizard 6y agoTo expand on this: Well maintained projects do not often push to `:latest`; They treat that tag like a `stable` version and push to it only public, stable releases. Roughly, it should always be max(semver), though practically it often trails when a new major release happens.
- donmcronald 6y ago> There is absolutely nothing special about `latest` > It simply happens to be the default tag when omitted That makes it special though, right? It's different than any other tag because it can be inadvertently pushed via accidental omission.