You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Marco Massenzio (JIRA)" <ji...@apache.org> on 2015/08/03 22:31:08 UTC
[jira] [Updated] (MESOS-3004) Design support running the command
executor with provisioned image for running a task in a container
[ https://issues.apache.org/jira/browse/MESOS-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marco Massenzio updated MESOS-3004:
-----------------------------------
Sprint: Mesosphere Sprint 15, Mesosphere Sprint 16 (was: Mesosphere Sprint 15)
> 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)