[
https://issues.apache.org/jira/browse/MESOS-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645059#comment-14645059
]
Timothy Chen commented on MESOS-3004:
-------------------------------------
Currently I've implemented a PoC the 2nd implementation option of running the
executor outside of the container filesystem. I was thinking one possible
problem with this approach was that the command executor might have problems
running if I chroot and it no longer can find its dependencies even though we
chroot in a fork. However, so far have successfully ran several tasks without
running any problem. Will like to get more community feedback if there are any
concerns with this approach!
> 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)
