Bump go-containerregistry to v0.21.7 to fix OOM during image extract#464
Merged
Julian Gutierrez Oschmann (juli4n) merged 2 commits intoJul 20, 2026
Conversation
Collaborator
|
It looks like you need to update licenses (./hack/update/licenses.sh). |
Collaborator
|
For the record, it would be good to also include a reference to the PR in go-containerregistry that fixes the described issue. |
Collaborator
Author
|
Thanks Julian Gutierrez Oschmann (@juli4n) — both addressed: LICENSES regenerated via |
mutate.Extract no longer holds every layer's decompressor and HTTP body open until the whole extraction finishes (fixes agent-substrate#120's memory spike on multi-GB images. Phase 0 of agent-substrate#463. Also pulls transitive bumps (docker/cli, klauspost/compress, x/sync, x/sys) and drops the now-removed estargz vendor tree (unused). EOF )
go-containerregistry v0.21.7 no longer depends on stargz-snapshotter/estargz, tar-split, or go-homedir; hack/update/licenses.sh removes their entries so hack/verify/licenses.sh passes.
Dmitry Berkovich (dberkov)
force-pushed
the
bump-go-containerregistry-v0.21.7
branch
from
July 20, 2026 04:56
4878555 to
eebc071
Compare
Dmitry Berkovich (dberkov)
requested a review
from Julian Gutierrez Oschmann (juli4n)
July 20, 2026 04:59
Julian Gutierrez Oschmann (juli4n)
approved these changes
Jul 20, 2026
Julian Gutierrez Oschmann (juli4n)
merged commit Jul 20, 2026
228fde4
into
agent-substrate:main
11 checks passed
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
2 participants
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.
Summary
Bumps
github.com/google/go-containerregistryv0.21.5 → v0.21.7. Phase 0 of #463.v0.21.6 fixed the memory spike in
mutate.Extractdescribed in #120 (upstream fix: google/go-containerregistry#2190, merged as google/go-containerregistry@38d6e4087c): extraction is now refactored into a per-layerextractLayerfunction, so each layer's decompressor and HTTP response body are closed as soon as that layer is processed, instead of all being held open via deferredClosecalls until the entire (multi-GB) extraction completes. atelet's pull path goes throughmemorypullcache.Fetch→mutate.Extract, so this directly caps its extract-time memory.Note this is only interim relief: #437's unbounded cache retention is untouched and is addressed by the redesign in #463.
Changes
go-containerregistryv0.21.5 → v0.21.7, plus required transitive bumps:docker/cli,klauspost/compress,golang.org/x/sync,golang.org/x/sysgo mod tidy+go mod vendor; thecontainerd/stargz-snapshotter/estargzvendor tree drops out (upstream removed the estargz integration; nothing in substrate used it), along withvbatts/tar-splitandmitchellh/go-homedirTesting
go build ./...passesgo test ./...passespkg/v1/mutate/mutate.goFixes #120
🤖 Generated with Claude Code