You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: