Repository navigation
Bump go-containerregistry to v0.22.1 - #120
Merged
Merged
Conversation
3 of 7 tasks
eriknordmark
force-pushed
the
ggcr-bump
branch
from
October 26, 2026 20:17
a7f4167 to
aebb1f4
Compare
christoph-zededa
approved these changes
Oct 27, 2026
zedUpload's OCI support pulled in docker/distribution through go-containerregistry v0.6.0, which uses that module's registry auth challenge parser. v0.22.1 has its own parser, so docker/distribution drops out of the dependency graph. That clears the Dependabot alert for CVE-2026-85747, which is in docker/distribution's registry client, a package eve-libs never compiled. v0.22.1 requires docker/go-connections v0.7.0, which removed sockets.DialPipe. The docker/docker v28 client that testcontainers-go v0.38.0 builds on still calls it, so the integration-tagged MinIO tests no longer compiled. testcontainers-go v0.44.0 uses the moby/moby client instead, and docker/docker leaves the dependency graph too. Signed-off-by: eriknordmark <erik@zededa.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
eriknordmark
force-pushed
the
ggcr-bump
branch
from
October 29, 2026 22:46
aebb1f4 to
67aaa20
Compare
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
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.
Description
Bumps go-containerregistry from v0.6.0 to v0.22.1. That version parses registry
auth challenges itself instead of importing
docker/distribution, sodocker/distributiondrops out ofgo.mod, which closes Dependabot alert #59(CVE-2026-85747). The vulnerable code,
docker/distribution's registry client,was never compiled into eve-libs: only
registry/client/auth/challengewas inthe build graph, and go-containerregistry checks fetched manifests against the
requested digest. So this is dependency hygiene, not a security fix.
Alongside go-containerregistry, MVS moves docker/cli, docker-credential-helpers,
docker/go-connections and klauspost/compress forward. None of the new versions
has a known advisory.
go-connections v0.7.0 removed
sockets.DialPipe, which the docker/docker v28client under testcontainers-go v0.38.0 still calls, so the integration-tagged
MinIO tests stopped compiling. testcontainers-go moves to v0.44.0, which uses the
moby/moby client, and docker/docker leaves
go.mod.lf-edge/eve#6926 makes the same bump in pillar. The two PRs do not depend on
each other.
How to test and validate this PR
go build ./...,go vet ./...andgo test -tags=integration ./...(thelast needs Docker for the MinIO container).
zedUpload/ociutilhas no unit tests, so the OCI path is exercised by EVE: deploy a container app
from a registry (for example docker.io) on an EVE build that vendors this change.