mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gastón Kleiman (JIRA) <j...@apache.org>
Subject [jira] [Commented] (MESOS-4113) Docker Executor should not set container IP during bridged mode
Date Mon, 28 Dec 2015 15:10:49 GMT

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

Gastón Kleiman commented on MESOS-4113:
---------------------------------------

Marathon v0.13.0 uses the host it extracts from Mesos offers used to create the task.

Marathon v0.14.0-RC1 tries to use the first address found in ContainerStatus.NetworkInfo.IPAddresses.
If NetworkInfo is missing or if it contains no addresses, then it falls back to using the
host it extracted from the offer that was used when it created the task.


> Docker Executor should not set container IP during bridged mode
> ---------------------------------------------------------------
>
>                 Key: MESOS-4113
>                 URL: https://issues.apache.org/jira/browse/MESOS-4113
>             Project: Mesos
>          Issue Type: Bug
>          Components: docker
>    Affects Versions: 0.25.0, 0.26.0
>            Reporter: Sargun Dhillon
>            Assignee: Artem Harutyunyan
>              Labels: mesosphere
>
> The docker executor currently sets the IP address of the container into ContainerStatus.NetworkInfo.IPAddresses.
This isn't a good thing, because during bridged mode execution, it makes it so that that IP
address is useless, since it's behind the Docker NAT. I would like a flag that disables filling
the IP address in, and allows it to fall back to the agent IP. 



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

Mime
View raw message