Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
When we use mknod to create device files within a container root, we require CAP_MKNOD in the root user namespace. If we have already entered a private user namespace, this fails with EPERM. To work around this, we can do what systemd-nspawn does (though for different reasons), which is to fall back bind mounting the device files into the chroot from the host.
Attachments
Issue Links
- blocks
-
MESOS-8142 Improve container security with user namespaces.
- Accepted