-
Notifications
You must be signed in to change notification settings - Fork 247
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
storage.conf: Don't specify nodev by default #208
Conversation
This reverts the default value of 8b1a0f8 but not the ability to specify options. Doing `nodev` on `/` breaks previously valid configurations, such as using `mock` inside a privileged container. While it's easy for such containers to learn to `mount -o remount,dev /`, it's a needless compatibility break. Rather, e.g. podman should learn to inject it only if it's known safe to do so (e.g. the target container doesn't have CAP_MKNOD anyways).
146fb66
to
669cb12
Compare
I actually want this for CRI-O more then podman, since running mock and having it create devices is not something we would do in mock. Why doesn't mock create a tmpfs for /dev? |
Reference?
You mean do in cri-o/Kubernetes? I think scheduling traditional build systems like Anyways, the point here is this broke compatibility, and today doesn't add any security. |
Running mock in Kubernetes should be done in a volume in the container not on the container image. |
I agree. But this change still broke my container, and doesn't really help anything today. |
It is my understanding that the Device Cgroup was not implemented in V2 cgroups. You are supposed to use some Seccomp/eBPF Filtering, I believe. |
If `nodev` is set, we should fail fast. See also containers/storage#208
If `nodev` is set, we should fail fast. See also containers/storage#208
If `nodev` is set, we should fail fast. See also containers/storage#208
If `nodev` is set, we should fail fast. See also containers/storage#208 Closes: #1604 Approved by: jlebon
tests are failing because the commit is missing |
I am closing this PR since @cgwalters can get what he wants from #226 |
This breaks previously valid configurations, such as using
mock
inside a privileged container. While it's easy forsuch containers to learn to
mount -o remount,dev /
, it's a needlesscompatibility break.
Rather, e.g. podman should learn to inject it only if it's known
safe to do so (e.g. the target container doesn't have CAP_MKNOD anyways).