[MESOS-6864] Container Exec should be possible with tasks belonging to a task group

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.2.0
• Labels: debugging mesosphere
• Target Version/s: 1.2.0
• Epic Link: Mesos Container Attach/Exec
• Sprint: Mesosphere Sprint 49
• Story Points: 5
• Assignee: Gastón Kleiman
• Reporter: Gastón Kleiman
• Shepherd: Anand Mazumdar
• Created: 05/Jan/17 18:40
• Updated: 20/Jan/17 00:55
• Resolved: 20/Jan/17 00:55

Description

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.

Issue Links

• blocks: MESOS-6280 Task group executor should support command health checks.
• duplicates: MESOS-6865 Remove the constraint of being only able to launch 2 level nested containers on Agent API