[
https://issues.apache.org/jira/browse/MESOS-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069968#comment-15069968
]
Jie Yu commented on MESOS-4113:
-------------------------------
To add some context here. I think it will be hard for Mesos to determine which
IP is routable and accessible from other hosts without operator's knowledge.
For instance, what if the docker container uses a custom network plugin? Also,
in NAT mode, using agent IP is not sufficient for accessing a given endpoint in
the container. The mapped port needs to be known as well. That means anyway you
need some other information in order to access the endpoint (relying on the IP
exposed in NetworkInfo alone is not sufficient). The best Mesos could do is to
do a best effort guess about the externally accessible IP for the container.
> 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)
