Skip to content

Document Dockerfile build secret limitations #1158

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
radiantjade wants to merge 1 commit into from
Closed

Document Dockerfile build secret limitations #1158

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions content/docs/builds/dockerfiles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,15 @@ FROM node
ARG RAILWAY_ENVIRONMENT
```

<Banner variant="warning">
Railway does not bind service variables as Docker BuildKit secrets for
`RUN --mount=type=secret`. Use `ARG` for build-time values in Dockerfile
builds, and avoid expanding secrets directly in `RUN` commands because the
expanded command can appear in build logs. Sealed variables hide values in the
Railway UI and API, but they do not prevent a Docker build step from printing a
secret after it has been expanded.
</Banner>

## Cache mounts

Railway supports cache mounts in your Dockerfile in the following format:
Expand Down
Loading