[
https://issues.apache.org/jira/browse/MESOS-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073005#comment-15073005
]
Jie Yu commented on MESOS-4113:
-------------------------------
Thanks [~gkleiman] for the explanation! That's clear now.
I think the framework shouldn't rely on the fact that the IP in network_info if
reachable since Mesos sometimes cannot decide if the IP is actually routable or
not without operator's knowledge (e.g., what if a custom docker network plugin
is used?). Marathon, in the case, knows that the container is using docker
BRIDGE mode and port mapping, so it should use the agent IP and the host port
to perform health check.
> 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)
