contentutil: add pull through cache for attestations chain resolve #6435
+527
−1
Conversation
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
tonistiigi
commented
Dec 20, 2025
| } | ||
| } | ||
| if _, ok := b.refs[wOpts.Ref]; ok { | ||
| b.mu.Unlock() |
Member
Author
There was a problem hiding this comment.
Unrelated possible deadlock.
Currently attestation chains were always loaded directly from registry on each pull. This adds cache capability to resolver so all the pulled manifests are first pulled to content store and kept there with GC labels references from the root manifest. If blob or referrers request already exists in the content store then local response is used without registry requests. Signed-off-by: Tonis Tiigi <[email protected]>
tonistiigi
force-pushed
the
attestation-chain-cache
branch
from
cf9b7c8 to
7e17a06
Compare
crazy-max
approved these changes
Jan 5, 2026
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.
Currently attestation chains were always loaded directly from registry on each pull.
This adds cache capability to resolver so all the pulled manifests are first pulled to content store and kept there with GC labels references from the root manifest.
If blob or referrers request already exists in the content store then local response is used without registry requests.