Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

llbsolver: tie op metadata to the op before recomputing digests #5563

Merged
merged 2 commits into from
Dec 3, 2024

Conversation

jsternberg
Copy link
Collaborator

@jsternberg jsternberg commented Dec 3, 2024

fixes #5558

When recomputing digests happens, the metadata is lost. This previously happened only with sources that were affected by source policies so it wasn't noticed, but now any LLB Op that is rewritten is affected since the gogo protobuf switch will cause all digests to be rewritten if the frontend and buildkit are using different versions.

When recomputing digests happens, the metadata is lost. This previously
happened only with sources that were affected by source policies so it
wasn't noticed, but now any LLB Op that is rewritten is affected since
the gogo protobuf switch will cause all digests to be rewritten if the
frontend and buildkit are using different versions.

Signed-off-by: Jonathan A. Sternberg <[email protected]>
@jsternberg jsternberg force-pushed the recompute-digests-fix-metadata branch from 700fcf7 to c644fb8 Compare December 3, 2024 19:09
@tonistiigi tonistiigi marked this pull request as draft December 3, 2024 19:12
@tonistiigi tonistiigi requested a review from cpuguy83 December 3, 2024 19:30
@tonistiigi tonistiigi marked this pull request as ready for review December 3, 2024 19:30
@tonistiigi tonistiigi added this to the v0.18.1 milestone Dec 3, 2024
@tonistiigi tonistiigi marked this pull request as draft December 3, 2024 19:35
@tonistiigi tonistiigi force-pushed the recompute-digests-fix-metadata branch from b6b8e75 to d1a3df3 Compare December 3, 2024 20:00
@tonistiigi tonistiigi marked this pull request as ready for review December 3, 2024 20:03
@tonistiigi
Copy link
Member

For the testing side, I added #5562 ,but the main issue is that this appears when client/frontend is on a different version than the daemon (when the proto marshal creates different results for them). We should try if we can run the CI from pinned frontend/test versions against the latest buildkit to catch issues like this early.

@tonistiigi tonistiigi merged commit a14b247 into moby:master Dec 3, 2024
96 checks passed
@jsternberg jsternberg deleted the recompute-digests-fix-metadata branch December 6, 2024 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

build with --no-cache not work after v0.17.2
4 participants