You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Anand Mazumdar (JIRA)" <ji...@apache.org> on 2017/01/05 19:17:58 UTC
[jira] [Updated] (MESOS-6864) Container Exec should be possible
with tasks belonging to a task group
[ https://issues.apache.org/jira/browse/MESOS-6864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anand Mazumdar updated MESOS-6864:
----------------------------------
Target Version/s: 1.2.0
Priority: Blocker (was: Major)
> 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)