[
https://issues.apache.org/jira/browse/MESOS-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370055#comment-16370055
]
ASF GitHub Bot commented on MESOS-8534:
---------------------------------------
Github user jdef commented on the issue:
https://github.com/apache/mesos/pull/263
What's the high level use case that's driving this change request? One of
the major goals of task-groups (pods) is to allow containers to share
networking and storage. What point is there in launching a nested container
that DOES NOT share these things with the other containers in the pod?
> Allow nested containers in TaskGroups to have separate network namespaces
> -------------------------------------------------------------------------
>
> Key: MESOS-8534
> URL: https://issues.apache.org/jira/browse/MESOS-8534
> Project: Mesos
> Issue Type: Task
> Components: containerization
> Reporter: Sagar Sadashiv Patwardhan
> Priority: Minor
> Labels: cni
>
> As per the discussion with [~jieyu] and [~avinash.mesos] , I am going to
> allow nested containers in TaskGroups to have separate namespaces. I am also
> going to retain the existing functionality, where nested containers can share
> namespaces with parent/root container.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
