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

Bind mounts doc should highlight renaming onto bindmounted files #9415

Closed
cflee opened this issue Sep 10, 2019 · 2 comments
Closed

Bind mounts doc should highlight renaming onto bindmounted files #9415

cflee opened this issue Sep 10, 2019 · 2 comments
Labels

Comments

@cflee
Copy link

cflee commented Sep 10, 2019

Problem description

This doc page currently doesn't highlight the caveat in the issue moby/moby#6011, which translated to the PR moby/moby#6854 which added a note to the docs. I can't seem to find anything similar in current docs. The note was present at least until v1.11, but I'm not sure where to find the exact point that it was gone.

It was quite surprising to run into this seemingly-undocumented behavior, where renaming or moving a file onto a bindmounted file, leads to container not being able to see the new file until it is restarted. The example given is sed, but other common tools that may do this include config mgmt tools like Ansible.

Problem location

File: storage/bind-mounts.md

Project version(s) affected

All versions?

Suggestions for a fix

Add a new subsection after "Mount into a non-empty directory on the container" that highlights this behaviour for files, since that's where another potentially-surprising behavior is mentioned, or add a paragraph to the initial section before the first heading. If this issue also affects directories, then that should be highlighted too.

@craig-osterhout craig-osterhout added the area/storage Relates to storage, volumes label Aug 3, 2022
@docker-robott
Copy link
Collaborator

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

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked

@docker docker locked and limited conversation to collaborators Jan 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants