-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Issue with podman : --volumes-from #23643
Comments
3.4. is ancient. We only supported the latest upstream release so please test with podman 5.2. |
@Luap99 |
You need to ask Ubuntu to update there version of Podman or switch to a distribution which is more up to date. |
see #17362, there are some third party repos listed that might work. |
Okay, thanks |
Hi @Luap99 : I am facing the same issue with podman version 5.2: APIVersion: 5.2.0 "-volumes-from" -doesnt work; Can you please let me know if something is missing; The folders in image doesnt get mounted onto the container. The same works for docker. podman create -v /test-repos --name testrepo localhost/testimage /bin/true podman run -it --network slirp4netns --volumes-from testrepo docker.io/library/ubuntu:22.04 /bin/bash podman run -it --network slirp4netns localhost/testimage:latest /bin/bash |
This works:
AFAICT copy up of volume content only happens on start time by default, you would need to set the |
Okay, thanks, this works! |
Issue Description
The podman ---volumes-from isnt mounting folders from exiting image created
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Files are missing when image volume is mounted onto the container
Describe the results you expected
At --volume-from mount; similar to docker; it should mount all files onto the container from image. Works properly in docker
podman info output
Podman in a container
Yes
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Ubuntu 22.04 machine used
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: