[
https://issues.apache.org/jira/browse/MESOS-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183423#comment-15183423
]
Dan Osborne commented on MESOS-4370:
------------------------------------
I don't believe this is entirely true. Regardless of whether the launched
container is using a User-defined Network or a regular docker networked
container, the place that Mesos expects to find the IP has been moved in the
docker api. Your fix addresses that, and restores Mesos ability to get the IP.
Though RA42516 also concerns networking, I don't think it should prevent this
from getting merged, as this will restore DNS and service discovery in Mesos
for Docker 1.10+
> NetworkSettings.IPAddress field is deprecated in Docker
> -------------------------------------------------------
>
> Key: MESOS-4370
> URL: https://issues.apache.org/jira/browse/MESOS-4370
> Project: Mesos
> Issue Type: Bug
> Components: containerization, docker
> Affects Versions: 0.25.0, 0.26.0, 0.27.0
> Environment: Ubuntu 14.04
> Docker 1.9.1
> Reporter: Clint Armstrong
> Assignee: Travis Hegner
>
> The latest docker API deprecates the NetworkSettings.IPAddress field, in
> favor of the NetworkSettings.Networks field.
> https://docs.docker.com/engine/reference/api/docker_remote_api/#v1-21-api-changes
> With this deprecation, NetworkSettings.IPAddress is not populated for
> containers running with networks that use new network plugins.
> As a result the mesos API has no data in
> container_status.network_infos.ip_address or
> container_status.network_infos.ipaddresses.
> The immediate impact of this is that mesos-dns is unable to retrieve a
> containers IP from the netinfo interface.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
