builder: do not set network.host entitlement flag if already set in buildkitd conf #2685
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.
follow-up #2683 (comment)
On container builder creation, it's possible to define buildkitd configuration path that will injected and used inside the container.
If insecure-entitlements opts are set in this configuration they will be skipped because we are always setting the
--allow-insecure-entitlement network.host
#2266 if user does not set it explicitly and buildkitd overrides configuration values with flags: https://github.com/moby/buildkit/blob/3a7055008a5e58a2abbe0e0c21c919d9e014e062/cmd/buildkitd/main.go#L583-L584.With this change we are now detecting if
network.host
insecure entitlement is set within the buildkitd configuration and skip setting--allow-insecure-entitlement network.host
flag.cc @dvdksn