[
https://issues.apache.org/jira/browse/MESOS-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652863#comment-14652863
]
Jie Yu commented on MESOS-3004:
-------------------------------
My proposal for solving this issue:
https://docs.google.com/document/d/1n2emC2ruTMur5nURvLgGYJxuP-tgBwgLDrmg_17QSmA/edit#
The main idea is to allow 'Volume' to specify an 'Image' as the source. The
provisioner is going to prepare the rootfs according to that. Mesos command
line executor will run under the host filesystem (i.e., not specify image in
ContainerInfo). The task image will be moved to a volume. The Mesos command
line executor will perform the root pivoting itself right before exec-ing the
user process.
> Design support running the command executor with provisioned image for
> running a task in a container
> ----------------------------------------------------------------------------------------------------
>
> Key: MESOS-3004
> URL: https://issues.apache.org/jira/browse/MESOS-3004
> Project: Mesos
> Issue Type: Improvement
> Components: containerization
> Reporter: Timothy Chen
> Assignee: Timothy Chen
> Labels: mesosphere
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
