You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2017/11/29 18:41:00 UTC
[jira] [Assigned] (MESOS-8272) Fall back to bind mounting container
devices.
[ https://issues.apache.org/jira/browse/MESOS-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Peach reassigned MESOS-8272:
----------------------------------
Assignee: James Peach
| [r/64170|https://reviews.apache.org/r/64170] | Fall back to binding devices if mknod fails. |
> Fall back to bind mounting container devices.
> ---------------------------------------------
>
> Key: MESOS-8272
> URL: https://issues.apache.org/jira/browse/MESOS-8272
> Project: Mesos
> Issue Type: Bug
> Components: containerization
> Reporter: James Peach
> Assignee: James Peach
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)