Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
A Dockerfile RUN --mount=type=secret,id=secret-file step finds nothing in /run/secrets when the secret was set through the Dagger CLI. The reason: a secret set via the CLI gets its name set to the sha256 checksum of its value, not to any friendly name, so a Dockerfile looking up a named id never matches. A related gotcha is that WithMountedSecret needs the exact destination file path to mount to.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Do not rely on the CLI-set secret name. Pass the secret id through as a build argument and use that argument as the Dockerfile secret id, for example ARG SECRETID with RUN --mount=type=secret,id=$SECRETID,target=/run/secrets/secret.txt. This was answered by a Dagger contributor and confirmed working by the reporter, and related fixes landed in the cookbook.
Source: https://github.com/dagger/dagger/issues/5242
Shows how to fix docker build secrets not visible in /run/secrets when set through the Dagger CLI. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes 'Zitadel folder not available' when building Zitadel through build/dockerfile by building via make docker_image instead, which compiles the binary first.
Walks through run kubectl after docker push in Google Cloud Build, step by step.