Skip to content

engine: 29.9.0 (moby docker-v29.9.0) - #532

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

zcsizmadia merged 3 commits into
mainfrom
deps/engine-29.9.0

Conversation

@zcsizmadia

Copy link
Copy Markdown
Collaborator

Bumps the engine to moby docker-v29.9.0 per docs/bumping-upstream.md.

  • MOBY_SHA a5b58c94d334674eae3a3207d4f05417643a90d0 (method verified by reproducing the 29.8.2 pin)
  • Go floor unchanged (1.26.8)
  • containerd/runc/buildkit unchanged, deliberately
  • 29.8.2 kept for rollback

The 29.9.0 checksums are empty until rootfs-v29.9.0-1 is published, so TestTheDefaultEngineShipsBothArchitectures and TestTheDefaultEngineResolvesOnThisHost are red by design. Checksums land in a second commit on this PR.

Bump moby to docker-v29.9.0 (a5b58c9). Go floor is unchanged at 1.26.8;
containerd, runc and buildkit are left alone. 29.8.2 stays listed for
rollback. The 29.9.0 checksums are empty until rootfs-v29.9.0-1 is
published, so the default-engine tests are red on this commit by design.
…rootfs is unreleased

The two default-engine checksum tests were red by construction on every
engine bump until the rootfs was published. They now skip with a
::warning:: on pull_request, and only when an empty checksum is the sole
problem; main and local runs still fail.
Verified by hashing the downloaded tarballs and comparing with the
published .sha256 assets.
zcsizmadia added a commit that referenced this pull request Oct 12, 2026
…u -version (#534)

docker run ... -version | head -1 closed the pipe while the docker CLI was
still writing the second line; under pipefail that failed some runs and
passed others (seen on the arm64 job of #532). Capture the output first.
@zcsizmadia
zcsizmadia merged commit 2e9b44a into main Oct 12, 2026
11 checks passed
@zcsizmadia
zcsizmadia deleted the deps/engine-29.9.0 branch October 12, 2026 13:59
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