-
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 4.x Pod volume mounts #13548
Comments
hm, I will look at this one. I am assuming there is some issue with the infra container design. |
I cannot reproduce this on the main branch @daynyxx have you tried building podman from the github repo and testing your issue? |
@cdoern build from main and still running into this problem. create pod: run ls on /test: result: run ls on /: result:
|
|
$ podman inspect -l --format '{{ .Mounts }}' |
@rhatdan it did work when I ran the command you used both with and without :Z. It did not work however when I used the absolute path
|
Please include a |
This is when mounting a folder
|
This is the result mounting a volume rather than a folder
|
Mounts are definitely unset for that container, so Podman did not add the mount. |
Any chance you can do a |
|
the infra Inherit function was not properly passing pod volume information to new containers alter the inherit function and struct to use the new `ConfigToSpec` function used in clone pick and choose the proper entities from a temp spec and validate them on the spegen side rather than passing directly to a config resolves containers#13548 Signed-off-by: cdoern <[email protected]> Signed-off-by: cdoern <[email protected]> Signed-off-by: cdoern <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When trying adding containers to a pod that has volume mounts, the containers do not have any of the volumes mounted
Steps to reproduce the issue:
podman run --pod=test fedora touch /test/test.file
Describe the results you received:
touch: cannot touch '/test/test.file': No such file or directory
The container will say the folder/file does not exist
Describe the results you expected:
The container will have the volume mounts from the pod it is a part of
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):podman-4.0.2-5.fc35.x86_64
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
This is running on my current desktop. The mounts do work when I mount them directly too the container. The latest documentation about the
podman pod create --volume
command here seems to imply that containers in that pod will all share the mounts defined in the create command, but that isn't working in my case. I have tried running with all of the propagation option as well.The text was updated successfully, but these errors were encountered: