Conversation
Podman 6 requires buildah 1.44, netavark/aardvark 2.0, skopeo 1.23, and config from container-libs common 0.68. Bump those, add containers-common and skopeo packages, and pin deb relationships so the stack upgrades as a unit. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Member
Author
|
Let's hold this until we're sure seedling and other workloads can cope. |
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.
🤖 Podman 6 has hard version requirements on the rest of the container stack:
This bumps the whole stack in lockstep and pins the deb relationships so apt can't leave any component behind.
Version bumps
cnibuild tag (CNI support was removed in v6; Netavark is now the only backend). Go 1.26.3 already satisfies v6's Go 1.25 minimum.New packages
containers/container-libsmonorepo at tagcommon/v0.68.0(config now lives there;containers/commonitself only reaches 0.64). Shipscontainers.confandseccomp.json(upstream), man pages (upstream), plus standardpolicy.json/registries.conf. It isArchitecture: allandProvides/Conflicts/ReplacesUbuntu'sgolang-github-containers-common, which is stuck at 0.57.x — too old for v6's rewritten config parser.containers_image_openpgp). Ships binary + man + completions only and depends oncontainers-commonforpolicy.json, avoiding a dpkg file conflict.Moving together
Podman 6 now
Depends: containers-common (>= 0.68), netavark (>= 2.0.0)andBreaksolder buildah/netavark/aardvark-dns/containers-common/skopeo. The other packages carry reciprocalBreaks: podman (<< 6.0.0), so the stack upgrades as a unit.Because
containers-common (>= 0.68)is a versioned dependency, buildah/podman from this repo now require this APT repo enabled to install (Ubuntu's virtualcontainers-commonis unversioned and can't satisfy it) — the intended lockstep behaviour.Plumbing
apt-repo.ymltriggers on and indexes both new packages (containers-common is synced into both arch pools since it is arch:all).skopeo/containers-commonand checkskopeo --versionand that the config files are present.