Rootful podman allows "unshare -r" in containers whereas docker disallows it #23955
Closed
chetan-reddy
started this conversation in
General
Replies: 2 comments
-
yes you can use the docker profile without issues |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks for the link. I searched the issues in this repo, but didn't realize that containers/common also has issues related to podman. Will search all the repos next time. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In a docker container, running
unshare -r
fails withunshare: unshare failed: Operation not permitted
. Rootful podman on the other hand allows it by default. I'm not too familiar with seccomp, but I think this is because podman's seccomp.json and docker's seccomp.json have different configuration forclone
Is it intentional to allow
unshare -r
in rootful podman? It seems like docker disallows it for good reason . If it is intentional, is there an easy way to disallow user namespaces in containers? I tried--sysctl=user.max_user_namespaces=0
but it fails withError: sysctl 'user.max_user_namespaces' not allowed
.Is it safe to just copy docker's seccomp.json and use it with podman? I tried it and it does work (disallows
unshare -r
), but I wanted to check with the experts if that's safe or if there was an easier way to accomplish my goal.Beta Was this translation helpful? Give feedback.
All reactions