[
https://issues.apache.org/jira/browse/MESOS-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Harutyunyan updated MESOS-6052:
-------------------------------------
Sprint: Mesosphere Sprint 41, Mesosphere Sprint 42 (was: Mesosphere Sprint
41)
> Unable to launch containers on CNI networks on CoreOS
> -----------------------------------------------------
>
> Key: MESOS-6052
> URL: https://issues.apache.org/jira/browse/MESOS-6052
> Project: Mesos
> Issue Type: Bug
> Components: containerization
> Affects Versions: 1.0.0
> Environment: Linux
> Reporter: Avinash Sridharan
> Assignee: Avinash Sridharan
> Labels: mesosphere
> Fix For: 1.1.0
>
>
> CoreOS does not have an `/etc/hosts`. Currently, in the `network/cni`
> isolator, if we don't see a `/etc/hosts` on the host filesystem we don't bind
> mount the containers `hosts` file to this target for the `command executor`.
> On distros such as CoreOS this fails the container launch since the
> `libprocess` initialization of the `command executor` fails cause it can't
> resolve its `hostname`.
> We should be creating the `/etc/hosts` and `/etc/hostname` files when they
> are absent on the host filesystem since creating these files should not
> affect name resolution on the host network namespace, and it will allow the
> `/etc/hosts` file to be bind mounted correctly and allow name resolution in
> the containers network namespace as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
