bake: global policy evaluation options#3832
Merged
Merged
Conversation
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
crazy-max
force-pushed
the
bake-policy-flag
branch
from
edfde4e to
da8fa45
Compare
tonistiigi
approved these changes
May 11, 2026
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.
fixes #3821
This adds a global
--policyflag todocker buildx bakefor invocation-level policy evaluation options. The flag supportsdisabled,strict, andlog-level, and it keeps policy file composition in the bake definition. The flag rejectsfilenameandreset, because those change policy composition and belong intarget.policy.The requested
--policy disabled=truebehavior is useful as a global escape hatch for a bake invocation. Keepingfilenameandresetout of the flag avoids mixing bake definition logic into a top-level runtime option.