You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Sagar Sadashiv Patwardhan (JIRA)" <ji...@apache.org> on 2018/02/16 01:17:00 UTC

[jira] [Comment Edited] (MESOS-8534) Allow nested containers in TaskGroups to have separate network namespaces

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

Sagar Sadashiv Patwardhan edited comment on MESOS-8534 at 2/16/18 1:16 AM:
---------------------------------------------------------------------------

[~alexr] Yes, this will affect both HTTP and TCP healthchecks. Let me figure what can be done to retain the existing functionality.


was (Author: sagar8192):
[~alexr] Yes, I think this will affect both HTTP and TCP healthchecks. Let me figure what can be done to retain the existing functionality.

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