Bump default containerd reference to release/2.3#466
Open
Eternity022 wants to merge 1 commit into
Open
Conversation
The default PKG_REF still tracked release/2.2 (v2.2.5) while upstream containerd has shipped v2.3.0–v2.3.2. Move the default to the release/2.3 branch and align GO_VERSION with the Go version pinned in containerd's release Dockerfile on that branch (1.26.4). Signed-off-by: Evangelos Bouzinis <v.bouzinis@hotmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bump default containerd ref to release/2.3
Why
The
_pkg-containerdbake target still defaults toPKG_REF = release/2.2(currentlycontainerd v2.2.5). Upstream has since shipped the v2.3 line (v2.3.0, v2.3.1, v2.3.2),
which is the new annual LTS branch. Nightly and default packaging builds should track the
current stable branch so v2.3.x packages can be produced.
What changed
Two lines in
docker-bake.hcl, target_pkg-containerd:PKG_REFdefault:release/2.2→release/2.3GO_VERSIONdefault:1.25.11→1.26.4(matches containerdrelease/2.3.github/workflows/release/Dockerfile; comment link updated accordingly)No other targets touched.
How tested
docker buildx bake validate— passes.pkg-containerd-debian12on the 2.3 ref (builtcontainerd.io.debwith Go 1.26.4).
pkg-containerd-{rhel8,rhel9,rhel10}+verify-containerd-*on the v2.3.2 ref(full results below).
Related
Actual releases are cut by maintainers via the
release-containerdworkflow_dispatch(
ref: vX.Y.Z), not by this PR. A follow-up issue asking maintainers to dispatch v2.3.2(and optionally back-fill v2.3.0/v2.3.1) is tracked in #467.
Test results
RPM build + verify matrix for containerd v2.3.2 (host: darwin/arm64, build platform
linux/arm64; amd64 remains covered by CI):All 10 stages passed. The v2.3.2 RPM binary embeds the correct upstream revision
fff62f1.