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
When I specify buildkitd-flags under setup-buildx-action@v3 in my workflow, workflow attempts to create a builder instance without specifying those flags.
I'm trying to add these flags because I noticed they were used in the default creation call (when I don't specifiy and with parameters). When I don't specify with parameters I'm able to create the builder, but when I try to use my cloud builder I get 400 errors (as seen in the logs)
The text was updated successfully, but these errors were encountered:
buildkitd-flags is not supported by drivers managing instances by themselves like cloud or remote. That being said we should still pass the flag on builder creation if user opt-in for it so the driver can error out.
For the error 2024-09-27T18:57:08.7246013Z ERROR: unknown builder: failed to fetch hub token: failed to get token, got: 400 Bad Request. Trace ID: . Response body: {"errinfo":{},"message":"malformed request"}, it seems the cloud instance ethanco/apollobuilder doesn't exist. Any idea @silvin-lubecki@fiam ?
For the error 2024-09-27T18:57:08.7246013Z ERROR: unknown builder: failed to fetch hub token: failed to get token, got: 400 Bad Request. Trace ID: . Response body: {"errinfo":{},"message":"malformed request"}, it seems the cloud instance ethanco/apollobuilder doesn't exist.
Contributing guidelines
I've found a bug, and:
Description
When I specify
buildkitd-flags
under setup-buildx-action@v3 in my workflow, workflow attempts to create a builder instance without specifying those flags.Expected behaviour
Under "Set up Docker Buildx"
Execute command
/usr/bin/docker buildx create --name builder-c93e3b66-fdf7-4cea-a3a8-a1d4c7b59797 --driver cloud --buildkitd-flags --allow-insecure-entitlement security.insecure --allow-insecure-entitlement network.host --use ethanco/apollobuilder
Actual behaviour
Command Executing:
/usr/bin/docker buildx create --name builder-c93e3b66-fdf7-4cea-a3a8-a1d4c7b59797 --driver cloud --use ethanco/apollobuilder
Repository URL
No response
Workflow run URL
No response
YAML workflow
Workflow logs
BuildKit logs
No response
Additional info
I'm trying to add these flags because I noticed they were used in the default creation call (when I don't specifiy and
with
parameters). When I don't specifywith
parameters I'm able to create the builder, but when I try to use my cloud builder I get 400 errors (as seen in the logs)The text was updated successfully, but these errors were encountered: