-
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
docs imply copy option should work for host directory mounts. #16961
Comments
@mheon PTAL |
Copy will not work on bind mounts, and we should throw an error. The issue is we don't want to copy content out of the image onto the volume since the volume is from the host, this is not something we want, and quite potentially not allowed. The intention for this option is for built in options where we create an empty directory, not for bind mount volumes. |
I'd also love to improve the documentation. It remains largely unclear what the option does (or I didn't find the right spot). |
Is this at all different for nfs volumes? |
Fixes: containers#16961 Signed-off-by: Daniel J Walsh <[email protected]>
@ykuksenko Copy works for any volume created by |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Podman run docs imply that the
copy
option should work on host directory mounts. This does not actually work.Steps to reproduce the issue:
Describe the results you received:
In the first podman command you get an empty directory.
Describe the results you expected:
The second podman command shows the contents that I expected to be there. Namely yum repo configs.
Additional information you deem important (e.g. issue happens only occasionally):
n/a
Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
orbrew info podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
libvirt/vagrant deployment of fedora 36
The text was updated successfully, but these errors were encountered: