You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2017/01/20 01:03:26 UTC
[jira] [Commented] (MESOS-6540) Pass the forked pid from
`containerizer launch` to the agent and checkpoint it.
[ https://issues.apache.org/jira/browse/MESOS-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830935#comment-15830935 ]
Adam B commented on MESOS-6540:
-------------------------------
No progress in a month. Dropping from the 1.2 release until somebody updates otherwise.
> Pass the forked pid from `containerizer launch` to the agent and checkpoint it.
> -------------------------------------------------------------------------------
>
> Key: MESOS-6540
> URL: https://issues.apache.org/jira/browse/MESOS-6540
> Project: Mesos
> Issue Type: Task
> Reporter: Kevin Klues
> Assignee: Kevin Klues
> Labels: debugging, mesosphere
>
> Right now the agent only knows about the pid of the "init" process forked by {{launcher->fork()}}. However, in order to properly enter the namespaces of a task for a nested container, we actually need the pid of the process that gets launched by the {{containerizer launch}} binary.
> Using this pid, isolators can properly enter the namespaces of the actual *task* or *executor* launched by the {{containerizer launch}} binary instead of just the namespaces of the "init" process (which may be different).
> In order to do this properly, we should pull the "init" process out of the container and update
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)