remotecache: fix inline cache used with multiple exporters #6263
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
When multiple exports run in parallel inline cache exporting can run for each of them into the same cache exporter instance. Inline cache exporter can only be invoked multiple times sequentially. There is a 'reset()` call after every invocation that completely switches out the internal cache chains collector. Before v0.25 this caused some corruption in inline cache (or some unknown error). Since v0.25 this case is likely to trigger internal consistency check error and fail the build. Signed-off-by: Tonis Tiigi <[email protected]>
4 tasks
crazy-max
approved these changes
Oct 4, 2025
hsw0
added a commit
to hsw0/test-devcontainer
that referenced
this pull request
Oct 7, 2025
Seems to fixed this bug - moby/buildkit#6263 ``` buildx failed with: ERROR: failed to build: failed to solve: failed to load ref: missing descriptor handlers for lazy blobs [sha256:...] ```
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.
fix #6256
When multiple exports run in parallel, inline cache exporting can run for each of them into the same cache exporter instance. Inline cache exporter can only be invoked multiple times sequentially. There is a 'reset()` call after every invocation that completely switches out the internal cache chains collector.
Before v0.25, this caused some corruption in the inline cache (or some unknown error). Since v0.25, this case is likely to trigger an internal consistency check error and fail the build.