Never ever use :latest unless its in your docker-compose DEV file. Try to treat docker images like you would dependencies.<p>We always lock down to specific versions, but we also use a self hosted docker mirror to cache everything anyway.
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<p>Edit:<p>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).
Was this untested or something?<p>I certainly don't see any unit tests as part of the commit that triggered this issue<p>(Yes, even, or perhaps especially, command line commands should be tested, somehow.)