Skip to content

v2.19.0

Latest

Choose a tag to compare

@amayer1983 amayer1983 released this 16 Nov 20:29
· 8 commits to main since this release

The first stable since August. It carries nine betas, and most of what is in it came out of a security audit of the whole tree — the detail was held back until now, because everyone on :latest was still running the old code.

A pinned container could be updated anyway. When the pin list could not be read, the part of Docksentry that actually updates containers decided nothing was pinned. An unreadable pin list now means everything is pinned, which is the direction that cannot cost you a database — and it says so in the log instead of stopping in silence.

A damaged settings file no longer opens the Web UI, kills the boot or stops the updates. Three separate ways one broken JSON file could hurt you, including a Web UI that opened the setup wizard to the next visitor after a restart. The damaged file is set aside, not deleted.

Updates that were never available. A container could be reported as updatable and then fail with pull access denied. An image lookup refused by docker-socket-proxy came back looking exactly like "this image has no digests". A refused lookup is now told apart from an empty one.

A failed pull says why, and you can give it more time. The one line explaining the failure sits at the end of what compose writes, and the end was the part that got cut off. The limit was also hardcoded at 1800 seconds since v1.7.0 — about 10.5 MB/s sustained for a 19 GB image. It is PULL_TIMEOUT now, up to 24 hours.

The update button in the Web UI answers. It started the update and said nothing at all.

Also in here: eleven settings can no longer take the container down with a typo, TLS on tcp://…:2376 works and the pre-flight agrees, /hosts check <endpoint> tells you whether a host would work before something fails, mail carries a Message-ID, a rate-limited notification is held rather than thrown away, and a release tag that disagrees with the code stops the build.

Full detail per beta in the changelog, and the beta release notes from 2.18.0-beta.36 onwards cover the same ground one step at a time.

If you are pinned to an old :X.Y.Z tag, note that the "a newer release exists" hint has been pointing at 2.17.7 since August — the changelog was missing its 2.18.0 section, which this release adds.