-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Podman behavior with shared volumes : copying files from mounted path #12714
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jan 3, 2022
Currently Docker copies up the first volume on a mountpoint with data. Fixes: containers#12714 Also added NeedsCopyUP, NeedsChown and MountCount to the podman volume inspect code. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jan 3, 2022
Currently Docker copies up the first volume on a mountpoint with data. Fixes: containers#12714 Also added NeedsCopyUP, NeedsChown and MountCount to the podman volume inspect code. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jan 4, 2022
Currently Docker copies up the first volume on a mountpoint with data. Fixes: containers#12714 Also added NeedsCopyUP, NeedsChown and MountCount to the podman volume inspect code. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jan 4, 2022
Currently Docker copies up the first volume on a mountpoint with data. Fixes: containers#12714 Also added NeedsCopyUP, NeedsChown and MountCount to the podman volume inspect code. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jan 6, 2022
Currently Docker copies up the first volume on a mountpoint with data. Fixes: containers#12714 Also added NeedsCopyUP, NeedsChown and MountCount to the podman volume inspect code. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Sep 21, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
/kind bug
Description
I don't know if this is "on purpose" but the behavior with named volumes is different between Docker and Podman.
If you mount an "empty" volume into a docker container to a new path (say "/opt/test") and then mount the same volume to another container to a "non-empty" path, then the content of the "non-empty" path will be copied on to the volume.
With Podman, the volume will remain "empty" as soon as it was mounted to one container.
Docker is more permissive and will allow the data to be copied if the volume is empty (even if it was mounted previously).
Steps to reproduce the issue:
Describe the results you received:
When running
ls
on the volume, that is to say either:ls /opt/test
in the first containerls /var
in the second containerThe folder is empty.
Describe the results you expected:
With Docker, the folder would contain the content copied from the
/var
directory of the centos:7 container.Additional information you deem important (e.g. issue happens only occasionally):
None
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Podman troubleshooting guide : YES
Podman lastest release (3.4.0) : NO
Additional environment details (AWS, VirtualBox, physical, etc.):
Running in Vagrant with Virtualbox provider.
The text was updated successfully, but these errors were encountered: