Skip to content

fix: correct bind mount example with conflicting WORKDIR #24125

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

Merged
dvdksn merged 1 commit into from
Feb 12, 2026
Merged

fix: correct bind mount example with conflicting WORKDIR #24125

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
11 changes: 7 additions & 4 deletions content/manuals/build/cache/optimize.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,13 +116,16 @@ instruction in your Dockerfile:

```dockerfile
FROM golang:latest
WORKDIR /app
WORKDIR /build
RUN --mount=type=bind,target=. go build -o /app/hello
```

In this example, the current directory is mounted into the build container
before the `go build` command gets executed. The source code is available in
the build container for the duration of that `RUN` instruction. When the
In this example, the current directory is mounted into the build container at
`/build` before the `go build` command gets executed. The build output is
written to `/app/hello`, which is outside the mount point. This distinction is
important: the build output must be written outside the bind mount target,
since the mount is read-only by default. The source code is available in the
build container for the duration of that `RUN` instruction. When the
instruction is done executing, the mounted files are not persisted in the final
image, or in the build cache. Only the output of the `go build` command
remains.
Expand Down