[MESOS-6540] Pass the forked pid from `containerizer launch` to the agent and checkpoint it.

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: debugging mesosphere
• Story Points: 2
• Assignee: Kevin Klues
• Reporter: Kevin Klues
• Created: 03/Nov/16 17:34
• Updated: 20/Jan/17 01:02

Description

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

Issue Links

• is blocked by: MESOS-6542 Pull the current "init" process for a container out of the container.