You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Qian Zhang (JIRA)" <ji...@apache.org> on 2016/08/26 07:16:20 UTC

[jira] [Commented] (MESOS-5544) Support running Mesos agent in a Docker container.

    [ https://issues.apache.org/jira/browse/MESOS-5544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438587#comment-15438587 ] 

Qian Zhang commented on MESOS-5544:
-----------------------------------

[~jieyu], Can you please let me know why the executor will be killed when the agent is crashes (even the agent is running in a Docker container with --pid=host)? I thought if the executor is launched by a framework with checkpoint enabled, it will be still there when the agent crashes.

> Support running Mesos agent in a Docker container.
> --------------------------------------------------
>
>                 Key: MESOS-5544
>                 URL: https://issues.apache.org/jira/browse/MESOS-5544
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Jie Yu
>
> Currently, this does not work if one tries to use Mesos containerizer.
> The main problem is that we want to make sure the executor is not killed when agent crashes. So we have to use --pid=host so that the agent is in the host pid namespace.
> But that is not sufficient, Docker daemon will put agent into all cgroups available on the host. We need to make sure we migrate the executor pid out of those cgroups so that when agent crashes, executors are not killed.
> Also, when start the agent container, volumes need to be setup properly so that any mounts under agent's work_dir will be propagate back to the host mount table. This is to make sure we can recover those mounts after agent restarts. This is also true for those mounts that are needed by some isolator (e.g., network/cni isolator).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)