You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2015/06/08 20:17:01 UTC
[jira] [Updated] (MESOS-2350) Add support for
MesosContainerizerLaunch to chroot to a specified path
[ https://issues.apache.org/jira/browse/MESOS-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone updated MESOS-2350:
------------------------------
Sprint: Twitter Mesos Q1 Sprint 3, Twitter Mesos Q1 Sprint 4, Twitter Mesos Q1 Sprint 5, Twitter Mesos Q1 Sprint 6, Twitter Q2 Sprint 1 - 4/13, Twitter Q2 Sprint 2, Twitter Q2 Sprint 3 - 5/11, Twitter Q2 Sprint 3, Twitter Q2 Sprint 4 (was: Twitter Mesos Q1 Sprint 3, Twitter Mesos Q1 Sprint 4, Twitter Mesos Q1 Sprint 5, Twitter Mesos Q1 Sprint 6, Twitter Q2 Sprint 1 - 4/13, Twitter Q2 Sprint 2, Twitter Q2 Sprint 3 - 5/11, Twitter Q2 Sprint 3)
> Add support for MesosContainerizerLaunch to chroot to a specified path
> ----------------------------------------------------------------------
>
> Key: MESOS-2350
> URL: https://issues.apache.org/jira/browse/MESOS-2350
> Project: Mesos
> Issue Type: Improvement
> Components: isolation
> Affects Versions: 0.21.1, 0.22.0
> Reporter: Ian Downes
> Assignee: Ian Downes
> Labels: twitter
>
> In preparation for the MesosContainerizer to support a filesystem isolator the MesosContainerizerLauncher must support chrooting. Optionally, it should also configure the chroot environment by (re-)mounting special filesystems such as /proc and /sys and making device nodes such as /dev/zero, etc., such that the chroot environment is functional.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)