Closed
Description
Contributing guidelines
- I've read the contributing guidelines and wholeheartedly agree
I've found a bug and checked that ...
- ... the documentation does not mention anything about my problem
- ... there are no open or closed issues that are related to my problem
Description
By default, buildx should use a default buildkitd config if it exists in any of the following locations:
$BUILDX_CONFIG/buildkitd.default.toml
$DOCKER_CONFIG/buildx/buildkitd.default.toml
~/.docker/buildx/buildkitd.default.toml
But it does not seem like buildx is interpreting this config at all.
Expected behaviour
Settings in e.g. ~/.docker/buildx/buildkitd.default.toml
should be automatically picked up with buildx create
Actual behaviour
buildkitd.default.toml
is ignored
Buildx version
github.com/docker/buildx v0.17.0 78c8c28
Docker info
No response
Builders list
NAME/NODE DRIVER/ENDPOINT STATUS BUILDKIT PLATFORMS
container* docker-container
\_ container0 \_ desktop-linux running 3a70550 linux/arm64, linux/amd64, linux/amd64/v2, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64, linux/arm/v7, linux/arm/v6
focused_cerf docker-container
\_ focused_cerf0 \_ desktop-linux inactive
default docker
\_ default \_ default running v0.15.2 linux/arm64, linux/amd64, linux/amd64/v2, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64
desktop-linux docker
\_ desktop-linux \_ desktop-linux running v0.15.2 linux/arm64, linux/amd64, linux/amd64/v2, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/mips64le, linux/mips64
cloud-docker-default cloud error
Configuration
# docker-bake.hcl
target default {
entitlements = ["security.insecure", "network.host"]
}
# ~/.docker/buildx/buildkitd.default.toml
insecure-entitlements = [ "network.host", "security.insecure" ]
$ docker buildx create --use
$ docker buildx bake --allow security.insecure --allow network.host
ERROR: failed to solve: granting entitlement security.insecure is not allowed by build daemon configuration
Build logs
No response
Additional info
No response