News for hackers. Stuff that matters.
Re:Dockerfile Security Best Practices by donmcronald on Wednesday October 14, 2020 @12:30PM (#24778493)
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/d...

Re:Dockerfile Security Best Practices by sfoley on Wednesday October 14, 2020 @12:51PM (#24778762)
There 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`.
Re:Dockerfile Security Best Practices by GauntletWizard on Wednesday October 14, 2020 @07:31PM (#24782990)
To 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.
Re:Dockerfile Security Best Practices by donmcronald on Wednesday October 14, 2020 @11:02PM (#24784449)
> 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.