other labels are mutable too though. That's why this broke for other tags beside latest. Use the hash instead for a hard link, but obviously won't get any security updates.
This is one of the reasons I never use the latest version of any docker image, so I don’t repeat my constant struggles with npm packages breaking on minor version changes
Edit:
I see they were overwriting current tags.... well that’s even worse
Ah yes, this happens from time to time when you use somebody else's
repositories with somebody else's package retention. That's why production
should only use repositories that change in ways that are predictable to you
(OS upstream, your own, and usually nothing else).
It's not standard, true, but it's also not an experimental feature, so one still wouldn't expect them to do wacky things like overwrite tags. I think many people expect version tagged code to not change, unless the developers specifically say they are nightly/experimental (there is a comment to that effect on the issue link).
[+] [-] bearjaws|8 years ago|reply
We always lock down to specific versions, but we also use a self hosted docker mirror to cache everything anyway.
[+] [-] moondev|8 years ago|reply
[+] [-] zackify|8 years ago|reply
Edit:
I see they were overwriting current tags.... well that’s even worse
[+] [-] Cthulhu_|8 years ago|reply
Overwriting tags should honestly not be possible, ever. Node / NPM did that (I think) with one of their versions too. Or was it a npm package?
[+] [-] dozzie|8 years ago|reply
[+] [-] timwis|8 years ago|reply
[+] [-] blablabla123|8 years ago|reply
[+] [-] pmarreck|8 years ago|reply
I certainly don't see any unit tests as part of the commit that triggered this issue
(Yes, even, or perhaps especially, command line commands should be tested, somehow.)
[+] [-] tkone|8 years ago|reply
[+] [-] lainga|8 years ago|reply
[+] [-] jlg23|8 years ago|reply