Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Thu, 3 Nov 2016 19:34:58 +0000 (UTC)
From: "Kevin Klues (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.13017758.1478194443000.177735.1478201698524@Atlassian.JIRA>
In-Reply-To: <JIRA.13017758.1478194443000@Atlassian.JIRA>
References: <JIRA.13017758.1478194443000@Atlassian.JIRA> <JIRA.13017758.1478194443836@arcas>
Subject: [jira] [Commented] (MESOS-6540) Pass the forked pid from
 `containerizer launch` to the agent and checkpoint it.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 03 Nov 2016 19:35:00 -0000


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

Kevin Klues commented on MESOS-6540:
------------------------------------

I agree with everything you said. 

For 1, though, I thought we agreed that the "short term workaround" would be to pass the pid of the forked process back to the agent somehow.  If not, what other solution are you proposing? The one where we just walk the process tree from the init process and find the first child in a different mount namespace and enter that one?

> 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)