You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jason Lai (JIRA)" <ji...@apache.org> on 2016/10/28 20:52:58 UTC

[jira] [Commented] (MESOS-6503) Mesos containerizer launch should not be pid 1 inside the container.

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

Jason Lai commented on MESOS-6503:
----------------------------------

Would be good to:
# make the `mesos-containerizer`'s launcher process live outside of the PID namespace like Docker containerd's shim process;
# the namespace unsharing should happen in the launcher's child process before `execv*(2)` into executors

> Mesos containerizer launch should not be pid 1 inside the container.
> --------------------------------------------------------------------
>
>                 Key: MESOS-6503
>                 URL: https://issues.apache.org/jira/browse/MESOS-6503
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Jie Yu
>
> This can solve two issues:
> 1) people cannot see arguments of mesos-containerizer launch
> 2) allow users to use other init system (e.g., systemd) inside the container



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