-
Notifications
You must be signed in to change notification settings - Fork 169
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
always set buildkitd-flags if opt-in #363
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make sure that the docs mention that if user sets buildkitd-flags
then the default is reset, and user might want to make sure set default again if they want that behavior.
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
2a6957d
to
214bb6d
Compare
@tonistiigi Done |
From what I can tell, this prevents clearing of
or any other falsy value will get disregarded, and the insecure entitlement flags will always get applied, which is unwanted in some situations. |
with v3.7.1 of setup-buildx-action setting any buildkit-flags overrides the default: docker/setup-buildx-action#363 we want to avoid that and neglect the debug flag
with v3.7.1 of setup-buildx-action setting any buildkit-flags overrides the default: docker/setup-buildx-action#363 we want to avoid that and neglect the debug flag
follow-up #357 (comment)
We should always pass
buildkitd-flags
if user opt-in for it and let the driver handle it. We just need to make sure the driver supportsbuildkitd-flags
if the input is not set to pass defaults.