-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
EPERM mounting sysfs with rootless/userns container #3672
Comments
I barely remember this depends on the kernel version, so some kernels (mistakenly) denied this mount. Two possible solutions are:
I am not sure what are the implications of bind-mounting host |
Now,
Based on these two points, I am closing this as not-a-bug. Let me know if you feel different. |
But Also, I'm happy to upgrade my kernel, but I'm using 5.15 -- the latest LTS -- which isn't exactly ancient. It's still what e.g. Ubuntu 22.04 is using/supporting for the next 5 years or so. |
Also, this reproduces on kernel 6.0.10 (Arch Linux)... |
OK, please tell us how to repro this (what is your environment and the steps to repro) and we'll take a look. |
There's not much more to to it than what I've reported here:
|
This is not runc bug, kernels denied this mount. this is right why crun can mount sysfs? because if in user namespace, crun bind /sys not sysfs |
I see; thanks! |
We should do the same for runc I guess |
I'm trying out
runc
to get a simple unpriviliged containerized execution, but am having issues mountingsysfs
:Meanwhile,
crun
manages fine:Full config
Binding
sys
instead works around the issue:The text was updated successfully, but these errors were encountered: