[jira] [Comment Edited] (MESOS-6864) Container Exec should be possible with tasks belonging to a task group

["Gastón Kleiman (JIRA)" <ji...@apache.org>]

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

Gastón Kleiman edited comment on MESOS-6864 at 1/19/17 4:42 PM:
----------------------------------------------------------------

https://reviews.apache.org/r/55676/
https://reviews.apache.org/r/55722/
https://reviews.apache.org/r/55677/
https://reviews.apache.org/r/55678/
https://reviews.apache.org/r/55679/
https://reviews.apache.org/r/55464/


was (Author: gkleiman):
https://reviews.apache.org/r/55464/

> Container Exec should be possible with tasks belonging to a task group
> ----------------------------------------------------------------------
>
>                 Key: MESOS-6864
>                 URL: https://issues.apache.org/jira/browse/MESOS-6864
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Gastón Kleiman
>            Assignee: Gastón Kleiman
>            Priority: Blocker
>              Labels: debugging, mesosphere
>
> {{LaunchNestedContainerSession}} currently requires the parent container to be an Executor (https://github.com/apache/mesos/blob/f89f28724f5837ff414dc6cc84e1afb63f3306e5/src/slave/http.cpp#L2189-L2211).
> This works for command tasks, because the task container id is the same as the executor container id.
> But it won't work for pod tasks whose container id is different from executor’s container id.
> In order to resolve this ticket, we need to allow launching a child container at an arbitrary level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)