[MESOS-3004] Design support running the command executor with provisioned image for running a task in a container

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: containerization
• Labels: mesosphere
• Epic Link: filesystem isolation
• Sprint: Mesosphere Sprint 15, Mesosphere Sprint 16
• Story Points: 5
• Assignee: Timothy Chen
• Reporter: Timothy Chen
• Created: 07/Jul/15 19:24
• Updated: 26/Nov/18 12:20
• Resolved: 26/Nov/18 12:20

Description

Mesos Containerizer uses the command executor to actually launch the user defined command, and the command executor then can communicate with the slave about the process lifecycle.
When we provision a new container with the user specified image, we also need to be able to run the command executor in the container to support the same semantics.
One approach is to dynamically mount in a static binary of the command executor with all its dependencies in a special directory so it doesn't interfere with the provisioned root filesystem and configure the mesos containerizer to run the command executor in that directory.