[
https://issues.apache.org/jira/browse/MESOS-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam B updated MESOS-6542:
--------------------------
Target Version/s: (was: 1.2.0)
> Pull the current "init" process for a container out of the container.
> ---------------------------------------------------------------------
>
> Key: MESOS-6542
> URL: https://issues.apache.org/jira/browse/MESOS-6542
> Project: Mesos
> Issue Type: Task
> Reporter: Kevin Klues
>
> Currently the mesos agent is in control of the "init" process launched inside
> of a container. However, in order to properly support things like
> systemd-in-a-container, we need to allow users to control the init process
> that ultimately gets launched.
> We will still need to fork a process equivalent to the current "init"
> process, but it shouldn't be placed inside the container itself (instead, it
> should be the parent process of whatever init process it is directed to
> launch).
> In order to do this properly, we will need to rework some of the logic in
> {{launcher->fork()}} to allow this new parent process to do the namespace
> entering / cloning instead of {{launcher->fork()}} itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
