centersl/docker-docs
1
0
Fork 0
mirror of https://github.com/docker/docs.git synced 2026-03-27 06:18:55 +07:00
Code Issues Packages Projects Releases Wiki Activity

Fix issue #24434: document secret mount behavior (#24442)

Browse Source 
Adds documentation explaining how secrets appear inside build containers
when using GitHub Actions secret mounts.

Changes:
- Added new section "How secrets appear in the build container"
explaining:
  - Default secret mount location (/run/secrets/<id>)
  - File permissions and content handling
  - How the env option works
  - Custom target paths
- Includes practical examples for both environment variable and
file-based secret access

Fixes #24434

---------

Co-authored-by: David Karlsson <dvdksn@users.noreply.github.com>
This commit is contained in:
David Karlsson
2026-03-23 17:25:04 +01:00
committed by GitHub
parent 2e28597412
commit e4259e32cd
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
content/manuals/build/ci/github-actions/secrets.md
View File

@@ -57,6 +57,13 @@ jobs:
"github_token=${{ secrets.GITHUB_TOKEN }}"
```
> [!NOTE]
> Secrets are mounted as files in the build container.
> By default, they're available at `/run/secrets/<id>`.
> You can also use the `env` option to load a secret into an environment variable,
> or the `target` option to customize the mount path.
> For details on secret mounts, see [Build secrets](/manuals/build/building/secrets.md).
### Using secret files
The `secret-files` input lets you mount existing files as secrets in your build.