Skip to content
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.

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

Build mounts guide + rw "discard" behavior #20549

Open
1 task done
milas opened this issue Aug 6, 2024 · 2 comments
Open
1 task done

Build mounts guide + rw "discard" behavior #20549

milas opened this issue Aug 6, 2024 · 2 comments
Assignees
Labels
area/build Relates to Dockerfiles or docker build command lifecycle/frozen

Comments

@milas
Copy link
Contributor

milas commented Aug 6, 2024

Is this a docs issue?

  • My issue is about the documentation content or website

Type of issue

I can't find what I'm looking for

Description

In the Dockerfile reference @ https://docs.docker.com/reference/dockerfile/#run---mounttypebind, the docs for the rw param mention:

Written data will be discarded.

This is not covered anywhere in the guide for build mounts, which leads to the assumption that they behave like run mounts, which are bi-directional.

Location

https://docs.docker.com/build/guide/mounts/

Suggestion

Add a short explanation about the use-case for read-write mounts with clarification that they do NOT propagate back to the host and that all "written data will be discarded".

@milas milas added the status/triage Needs triage label Aug 6, 2024
@dvdksn dvdksn self-assigned this Aug 7, 2024
@dvdksn dvdksn added area/build Relates to Dockerfiles or docker build command and removed status/triage Needs triage labels Aug 7, 2024
@dvdksn
Copy link
Contributor

dvdksn commented Aug 7, 2024

Cheers @milas - good callout! I agree that this deserves clarification, it's in my todo pile.

@docker-robot
Copy link

docker-robot bot commented Nov 5, 2024

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build Relates to Dockerfiles or docker build command lifecycle/frozen
Projects
None yet
Development

No branches or pull requests

2 participants