Skip to content

engine: rootfs 29.9.0-2, built with Go 1.26.9 - #536

Merged
zcsizmadia merged 3 commits into
mainfrom
engine/29.9.0-rev2
Oct 12, 2026
Merged

zcsizmadia merged 3 commits into
mainfrom
engine/29.9.0-rev2

Conversation

@zcsizmadia

Copy link
Copy Markdown
Collaborator

moby builds docker-v29.9.0 with Go 1.26.9, whose runtime update is the release's headline security fix (CVE-2026-97032, -78659, -78663, -78669: HTTP/2 DoS in dockerd; CVE-2026-56857: Windows junction). We pinned GO_VERSION at moby's go.mod floor (1.26.8), so rootfs-v29.9.0-1 does not have them: I read go1.26.8 out of the dockerd in its published tarball.

  • GO_VERSION=1.26.9 (golang:1.26.9-alpine/bookworm both exist), ROOTFS_REVISION=2
  • manifest points the default engine at rootfs-v29.9.0-2, checksums empty until published (default-engine tests skip on the PR, by design)
  • -1 stays published (assets are immutable)
  • not changed: containerd/runc/buildkit, and the docker CLI's own GO_VERSION (separate stream)

Process gap, to fix in docs/bumping-upstream.md: step 2 checks the Go floor only. It should also compare against the Go version moby's own Dockerfile builds with.

moby builds docker-v29.9.0 with Go 1.26.9, which fixes five stdlib CVEs in
dockerd (four HTTP/2 DoS, one Windows junction escape). Our GO_VERSION was
pinned at the go.mod floor (1.26.8), so rootfs 29.9.0-1 -- verified by
reading the go version out of its dockerd -- does not have them.

GO_VERSION 1.26.9, ROOTFS_REVISION 2. Checksums are empty until
rootfs-v29.9.0-2 is published; the default-engine tests skip on the PR.
Verified by hashing the downloaded tarballs against the published .sha256
assets; dockerd, containerd and buildkitd in the tarball report go1.26.9.
@zcsizmadia
zcsizmadia merged commit 450c1f4 into main Oct 12, 2026
11 checks passed
@zcsizmadia
zcsizmadia deleted the engine/29.9.0-rev2 branch October 12, 2026 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant