Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Mon, 18 Jul 2016 16:46:20 +0000 (UTC)
From: "Jie Yu (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12987642.1467936610000.60720.1468860380583@Atlassian.JIRA>
In-Reply-To: <JIRA.12987642.1467936610000@Atlassian.JIRA>
References: <JIRA.12987642.1467936610000@Atlassian.JIRA> <JIRA.12987642.1467936610605@arcas>
Subject: [jira] [Updated] (MESOS-5806) CNI isolator should prepare network
 related /etc/* files for containers using host mode but specify container
 images.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 18 Jul 2016 16:46:27 -0000


     [ https://issues.apache.org/jira/browse/MESOS-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jie Yu updated MESOS-5806:
--------------------------
          Sprint: Mesosphere Sprint 39
    Story Points: 3

> CNI isolator should prepare network related /etc/* files for containers using host mode but specify container images.
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-5806
>                 URL: https://issues.apache.org/jira/browse/MESOS-5806
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization, network
>            Reporter: Jie Yu
>            Assignee: Qian Zhang
>              Labels: mesosphere
>             Fix For: 1.0.0
>
>
> Currently, the CNI isolator will just ignore those containers that want to join the host network (i.e., not specifying NetworkInfo). However, if the container specifies a container image, we need to make sure that it has access to host /etc/* files. We should perform the bind mount for the container. This is also what docker does when a container is running in host mode.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)