3 ms·
As Kelsey Hightower once said "latest is not a version" You should always pin versions to something specific. I had to deal with new versions breaking things
by verdverm 4y ago
As Kelsey Hightower once said "latest is not a version"
You should always pin versions to something specific.
I had to deal with new versions breaking things twice this week. One was the Docker Go client, which while pinned, updated to 23 and broke things. Had to roll it back, which goes to show you even pinning versions does not prevent these issues, though in your case, you would have known by being intentional. Of course, now you have the version update chores...
---
Docker changelog: https://docs.docker.com/engine/release-notes/23.0/ https://docs.docker.com/engine/release-notes/23.0/ (published before the release, available for many weeks if you pay attention on GitHub)
- bionsystem 4y agoThe problem is that I don't control our production systems as they are on-prem on clients sites. Meaning that any of my client can run "apt update && apt upgrade" and I'm screwed regardless of what I do. This is in fact a good reason to keep "latest" on my side so that I know first-hand when things break.
- bionsystem 4y agoThe changelog was put online after the new version was released, too.
- verdverm 4y agoThe release notes were published on Feb 1, the assets on Feb 2
- bionsystem 4y agoThat seems to be true, I guess I checked on the wrong link on feb 2.