-
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
'Permission denied' on volumes in Mac OS with podman machine #17560
Comments
I am facing a very similar issue on my own system. This has started occuring only from the past few days Could someone help here? |
I also ran into this issue after upgrading to podman 4.4.1 on M1 Mac.
I'm running docker.io/elasticsearch:7.17.9 container which tries to 'chroot --userspec=1000:0 /' and fails with 'chroot: cannot change root directory to '/': Operation not permitted'. |
In my case, adding SYS_CHROOT capability fixed it. It looks like podman changed default container capabilities in 4.4. |
Yes. Not sure the other reporters are complaining about chroot. |
It fails for me with the error |
--cap-add sys_chroot fixes this issue. But that is not what @ReeSilva was reporting above. |
A friendly reminder that this issue had no activity for 30 days. |
Since we have heard no further input closing. |
@rhatdan what kind of input do you need? The problem still exists :/ Can we reopen the issue? |
Did --cap-add CAP_CHROOT work for you? |
I can reproduce the issue reported by @ReeSilva on a Mac M1 with podman client 4.4.4 and podman server 4.4.2. Adding |
I'm seeing the same issue and would say that chroot is unrelated. |
Nope, |
I have the same issue on M2 Mac and vscode. Adding --cap-add CAP_SYS_CHROOT did not help too. |
If you use |
@Luap99 Outstanding. Saw this tip on the troubleshooting when opened the issue but neither with this was working, maybe another config was wrong. Really really thanks for that. I'll test it later on Windows and Linux as well, but probably will work as well. |
Intel macos 12.6.2 add --userns=keep-id:uid=${UID} works |
Issue Description
When running
dev cointaner
on Visual Studio Code, the volume mounted on the container getpermission
denied when trying to write, even with--userns=keep-id
. The user ID on Mac OS (502) is the same as the usercore
on the VM.Without
--userns=keep-id
the volume is mounted with ownerroot
. Using--userns=keep-id
the volume is mounted with the usercore
. This happens because my user ID on Mac (502) Is the same as the usercore
on the VM where podman runs.The same error happens if running from command line the same way vscode runs the container.
Steps to reproduce the issue
Steps to reproduce the issue
--userns=keep-id
:podman container run -v (pwd)/golive:/workspace/golive --rm -it --user=1000 --userns=keep-id golang bash
cd /workspace/golive
touch test
Describe the results you received
touch: cannot touch 'test': Permission denied
Describe the results you expected
File should be created.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Additional environment details
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: