mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Yu (JIRA)" <>
Subject [jira] [Commented] (MESOS-6156) Make the `network/cni` isolator nesting aware
Date Thu, 22 Sep 2016 01:34:20 GMT


Jie Yu commented on MESOS-6156:

commit 2a8de6255494eed2c435ef2b80dc846e1c1b5e90
Author: Avinash sridharan <>
Date:   Wed Sep 21 17:16:37 2016 -0700

    Modified the `network/cni` isolator to be nesting aware.
    The network file setup in the `network/cni` isolator is now nesting
    aware. Since the children share the network and UTS namespace with the
    parent, the network files need to be created only for the parent
    container. For the child containers, the network files will be simply
    a bind mount of the parents network files.

> Make the `network/cni` isolator nesting aware
> ---------------------------------------------
>                 Key: MESOS-6156
>                 URL:
>             Project: Mesos
>          Issue Type: Task
>          Components: containerization
>    Affects Versions: 1.1.0
>            Reporter: Avinash Sridharan
>            Assignee: Avinash Sridharan
>              Labels: mesosphere
>             Fix For: 1.1.0
>   Original Estimate: 96h
>  Remaining Estimate: 96h
> In pods, child containers share the network and UTS namespace with the parent containers.
This implies that during `prepare` and `isolate` the `network/cni` isolator needs to be aware
the parent-child relationship between containers to make the following decisions:
> a) During `prepare` a container should be allocated a new network namespace and UTS namespace
only if the container is a top level container.
> b) During `isolate` the network files (/etc/hosts, /etc/hostname, /etc/resolv.conf) should
be created only for top level containers. The network files for child containers will just
be symlinks to the parent containers network files.

This message was sent by Atlassian JIRA

View raw message