build: forward all build opts everywhere #1476
Merged
Conversation
This file contains 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
approved these changes
Dec 15, 2022
All build options should be passed everywhere - the frontend and the backend of buildkit should both be able to see all attestations, as well as all other opts: e.g. epoch settings, and no-cache. Signed-off-by: Justin Chadwell <[email protected]>
jedevc
force-pushed
the
dont-filter-attestation-opts
branch
from
d23abc8
to
a8f689c
Compare
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.
All build options should be passed everywhere - the frontend and the backend of buildkit should both be able to see all attestations, as well as all other opts: e.g. epoch settings, and no-cache.
Essentially, this is the buildx equivalent of the logic in buildkit: moby/buildkit@8edf57d