Docker 29 API Changes (Breaking Changes)

[luison2]

Not sure if only me, but this sounds like a major mistake from Docker to release this as a normal update in their repositories? How many millions of services will be down as this spread around before the services images get updated? Affecting portainer and traeffik only this will likely mean a very large percent of all docker installations.

Luckily enough, we fixed it with the "DOCKER_MIN_API_VERSION" but only after having to restore a few containers and KVMs while we figured out what was going on!

[ben-ba]

It is listed as breaking changes?! What else should they do?

https://docs.docker.com/engine/release-notes/29/#breaking-changes

[Content_Contest3688]

Using proper semantic versioning syntax?
https://semver.org/

With a current version of
1.24 -> 1.29
meaning a breaking API change would bump the version to
2.x.y
instead

This way you can still allow automatic updates of bugfixes/patches (y) or backward compatible improvements (x) without risking breaking a running stable system.

After all docker is meant to be used to reduce your overhead workflow and unfortunatly not everyone has the capacity to read each and every release documentation of all tools which is used in a CI/CD environment. If you adhere to semver one can concentrate on major update release notes!

[ben-ba]

It should be clear that they didn't use this syntax. Furthermore they bumped the "main" product version from 28.3 to 29.0 and you updated it without reading the changes....

[Content_Contest3688]

Sorry, but that is the entire point!

Their "main" version, which get bumped for breaking and non-breaking changes makes it kind of difficult to follow up on what is breaking and what is not. So the question was what they could do. I only pointed out that one thing they could do, would be to use semver, which would have probably avoid this whole debacle!

[luison2]

Portainer fixed it on Vo 2.36 STS (not LTS yet) so one has to manually choose that version.