[
https://issues.apache.org/jira/browse/MESOS-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069471#comment-15069471
]
Sargun Dhillon edited comment on MESOS-4113 at 12/23/15 10:22 AM:
------------------------------------------------------------------
The information that's exposed by MESOS-4064 allows for a external program to
analyze the state.json and determine what IP to use. Specifically, it parses to
see if the task / executor has a docker container in bridged mode. If it's in
the mode, it uses the slaveID field to lookup the relevant slave, and then
parses the PID. Currently, Minuteman, and Mesos-DNS both do this.
I believe we should have another NetworkInfos field that actually determines
the definitive IPs that external users can contact in order to connect to the
task, because NetworkInfos as they are today are effectively useless, due to
the behaviour under Docker containers.
was (Author: sargun):
The information that's exposed by MESOS-4064 allows for a external program to
> 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)
