[MESOS-2350] Add support for MesosContainerizerLaunch to chroot to a specified path

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.21.1, 0.22.0
• Fix Version/s: 0.24.0
• Component/s: containerization
• Labels: twitter
• Target Version/s: 0.24.0
• Epic Link: filesystem isolation
• 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 Mesos Q2 Sprint 5, Twitter Mesos Q2 Sprint 6, Twitter Mesos Q3 Sprint 1
• Story Points: 5
• Assignee: Ian Downes
• Reporter: Ian Downes
• Created: 12/Feb/15 05:44
• Updated: 26/Apr/17 16:54
• Resolved: 08/Jul/15 21:21

Description

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.

Issue Links

• blocks: MESOS-2540 mesos containerizer should provide scheduler specified rootfs
• supercedes: MESOS-349 remove mounts when garbage collecting tasks