You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... the documentation does not mention anything about my problem
... there are no open or closed issues that are related to my problem
Description
I have a docker-bake.hcl that passes SSH to the build. On the latest buildx version, this produces a warning when I run docker buildx bake and says I should add --allow=ssh to resolve the warning. However, if I add that, the warning stays.
Expected behaviour
No warning after adding --allow=ssh
Actual behaviour
It sees the --allow=ssh, but prompts to add it again:
[+] Building 0.0s (1/1) FINISHED docker:default
=> [internal] load local bake definitions 0.0s
=> => reading docker-bake.hcl 42B / 42B 0.0s
Your build is requesting privileges for following possibly insecure capabilities:
- Forwarding default SSH agent socket
In order to not see this message in the future pass "--allow=ssh" to grant requested privileges.
Your full command with requested privileges:
docker buildx bake --allow=ssh --allow=ssh
This warning will become an error in a future release. To enable filesystem entitlements checks at the moment, set BUILDX_BAKE_ENTITLEMENTS_FS=1 .
[+] Building 0.7s (7/7) FINISHED docker:default
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 145B 0.0s
=> [internal] load metadata for docker.io/library/alpine:latest 0.7s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [default 1/3] FROM docker.io/library/alpine:latest@sha256:56fa17d2a7e7f168a043a2712e63aed1f8543aeafdcee47c58dcffe38ed51099 0.0s
=> CACHED [default 2/3] RUN apk update && apk add openssh 0.0s
=> CACHED [default 3/3] RUN --mount=type=ssh ssh -v [email protected] || true 0.0s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:c6a62c3d95e9e04f0081719b56a6ec0f44faa4646c33b4cee07103bc75aca07a
FROM alpine AS default
RUN apk update && apk add openssh
RUN --mount=type=ssh ssh -v [email protected] || true
target"default" {
ssh=["default"]
}
Build logs
[+] Building 0.0s (1/1) FINISHED docker:default
=> [internal] load local bake definitions 0.0s
=> => reading docker-bake.hcl 42B / 42B 0.0s
Your build is requesting privileges for following possibly insecure capabilities:
- Forwarding default SSH agent socket
In order to not see this message in the future pass "--allow=ssh" to grant requested privileges.
Your full command with requested privileges:
docker buildx bake --allow=ssh
This warning will become an error in a future release. To enable filesystem entitlements checks at the moment, set BUILDX_BAKE_ENTITLEMENTS_FS=1 .
[+] Building 0.3s (7/7) FINISHED docker:default
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 145B 0.0s
=> [internal] load metadata for docker.io/library/alpine:latest 0.3s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [default 1/3] FROM docker.io/library/alpine:latest@sha256:56fa17d2a7e7f168a043a2712e63aed1f8543aeafdcee47c58dcffe38ed51099 0.0s
=> CACHED [default 2/3] RUN apk update && apk add openssh 0.0s
=> CACHED [default 3/3] RUN --mount=type=ssh ssh -v [email protected] || true 0.0s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:c6a62c3d95e9e04f0081719b56a6ec0f44faa4646c33b4cee07103bc75aca07a
Additional info
To my understanding, I don't think that this is a duplicate of #2895 because that seems to be adding the support for the entitlements keyword in HCL, rather than on the CLI.
The text was updated successfully, but these errors were encountered:
Contributing guidelines
I've found a bug and checked that ...
Description
I have a docker-bake.hcl that passes SSH to the build. On the latest buildx version, this produces a warning when I run
docker buildx bake
and says I should add--allow=ssh
to resolve the warning. However, if I add that, the warning stays.Expected behaviour
No warning after adding --allow=ssh
Actual behaviour
It sees the --allow=ssh, but prompts to add it again:
Buildx version
github.com/docker/buildx v0.19.3 48d6a39
Docker info
Builders list
Configuration
Build logs
Additional info
To my understanding, I don't think that this is a duplicate of #2895 because that seems to be adding the support for the entitlements keyword in HCL, rather than on the CLI.
The text was updated successfully, but these errors were encountered: