-
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
support "--security-opt systempaths=unconfined" #7537
Comments
We already support passing options to the |
This is separate to procfs mount options. This is about disabling the |
Ah - I see, you're entirely right. This is definitely worth adding. |
@cyphar, do you have cycles to open a PR? |
I'll write something up this week. |
A friendly reminder that this issue had no activity for 30 days. |
@umohnani8 PR to handle --security-opt=mask/unmask should fix this Issue. @umohnani8 We might want to add a unmask=all flag to remove all masking. |
Yup, we have |
Uh this isn't quite fixed because you don't have flag-parity with Docker but I can send a PR to fix that up. |
SGTM |
Opened #8630 for the flag-parity |
/kind feature
Description
Right now you can't disable the
/proc
overmounts. While these are a security feature in general, due to kernel restrictions, this means that you cannot run a subcontainer or other sandbox that tries to mountprocfs
(even if it uses user namespaces). Having a way to optionally disable this would be neat and would also bring more feature parity with Docker (which supports--security-opt systempaths=unconfined
).In newer kernels you will be able to work around this with
mount -t procfs -o subset=pids procfs /proc
but right now the only other workaround is to mount some/proc
handle into the container. The safest way is with something like:But most people probably end up doing
/proc:/.stashed-proc
which is quite dangerous. This is also probably needed to completely supportAllowedProcMountTypes = Unmasked
.The text was updated successfully, but these errors were encountered: