[
https://issues.apache.org/jira/browse/MESOS-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15633681#comment-15633681
]
Jie Yu commented on MESOS-6540:
-------------------------------
aha, ic. It can just be a pipe (rather than a domain socket).
> 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).
> This will involve opening a domain socket with the {{containerizer launch}}
> binary and passing the translated pid from the forked process back to the
> agent. We can chieve this by opening the socket on the agent and passing the
> path to it using {{launchFlags}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
