[
https://issues.apache.org/jira/browse/MESOS-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662687#comment-14662687
]
Jie Yu commented on MESOS-3004:
-------------------------------
commit d9443935557a9254d68625fadd1c6e5d0f268a3f
Author: Jie Yu <[email protected]>
Date: Mon Aug 3 16:07:33 2015 -0700
Added Image to Volume as one of the sources.
Review: https://reviews.apache.org/r/37055
commit ddfab613acdb998ede64d80abeb49300a88959c4
Author: Jie Yu <[email protected]>
Date: Mon Aug 3 13:04:44 2015 -0700
Moved ContainerInfo::Image definition to the top level.
Review: https://reviews.apache.org/r/37054
> 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)
