-
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
Macosx default machine issues with nested podman. #25265
Comments
You cannot use virtiofs as container storage path which means you cannot use host paths for them. I suggest you use a normal volume instead |
I'm sorry, not following. this works fine on linux hosts. what is the technical issue here that prevents it from working on macosx? aka what is podman/crun/whatever doing differently that results in the difference in behavior I manually create files but get permission denied when podman tries to write to the directory? What is your definition of a 'normal' volume vs --volume src:dst:rw? Basically, if i go strace what am I going to find podman doing that causes it to fail here. |
Because you are not using virtiofs on your normal linux. Like I said the host paths that ar emounted on th emachine VM are not suitable for a contianer store. If you mount another path from the VM it can work. The easiest is to use podman volumes |
What are the limitations with virtiofs that cause this? again these are straight up writes to the directory and I can write to these folders just fine from the same environment were podman build fails, its the podman command having the issue. It doesn't seem to me that virtiofs is problematic, it seems like podman and the underlying code/libraries are doing something odd. As a end user (and developer) this looks 100% like a bug both the mismatch in behavior between host OS's and the mismatch in behavior between podman and other programs on the macosx host. edit: please note: I appreciate the suggestions for alternative approaches. but they require more complexity for end users or more specialization by developers. I'm trying to drill into why podman is behaving this way and determining if its an actual technical limitation or just 'its hard'. From a personal point of view I don't see why there would be a difference between creating a volume via podman which at its core is still FS managed by the host and just using --volume directly on a directory. |
Issue Description
Attempting to run nested podman containers in the macosx podman-default-machine and running into permissions issues when writing the containers to a mounted folder:
Steps to reproduce the issue
Describe the results you received
doesnt work; but works fine on linux systems:
Describe the results you expected
expected the container to be pulled and stored successfully.
podman info output
Podman in a container
Yes
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
macosx host. applehv provider.
Additional information
pretty much at a loss for this atm. these fixes might resolve it? its unclear.
in the podman default machine it looks like the Options typo was fixed. 🤷
The text was updated successfully, but these errors were encountered: