Persistent allow=fs.read entitlement?

[milas]

I mount files outside the build context ($HOME/.netrc), so I get warnings with the new buildx version.

Running docker buildx bake (without arguments) is really convenient, I don't want to have to pass --allow=fs.read=/Users/milas/.netrc on every command. I understand the security angle, but UX-wise, this is a bit lacking.

Can I:

• Globally permit specific path(s) via buildkitd.toml or similar?
• Specify via an environment variable (BUILDKIT_ALLOW_FS_READ=/Users/milas/.netrc)?

Your build is requesting privileges for following possibly insecure capabilities:

 - Read access to path /Users/milas/.netrc

In order to not see this message in the future pass "--allow=fs.read=/Users/milas/.netrc" to grant requested privileges.

Your full command with requested privileges:

docker buildx bake --allow=fs.read=/Users/milas/.netrc

This warning will become an error in a future release. To enable filesystem entitlements checks at the moment, set BUILDX_BAKE_ENTITLEMENTS_FS=1 .

[Kxrma47]

There is currently no persistent per-path allowlist in buildkitd.toml: fs.read is a Bake client-side entitlement, so it must be granted on the Bake invocation. A small wrapper keeps the permission explicit without retyping it:

#!/bin/sh
exec docker buildx bake --allow 'fs.read=/Users/milas/.netrc' "$@"

This is intentionally separate from BuildKit daemon entitlements such as network.host and security.insecure. The supported filesystem forms are documented here: https://docs.docker.com/reference/cli/docker/buildx/bake/#allow-extra-privileged-entitlement---allow