[
https://issues.apache.org/jira/browse/MESOS-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069446#comment-15069446
]
Bernd Mathiske commented on MESOS-4113:
---------------------------------------
@scalp42, thanks for being persistent! I don't see either how MESOS-4064 can be
viewed as a duplicate of this issue here. I suspect it was closed assuming the
"duplicate" link is correct. Further indication for this is that AFAICT none of
the code in the reviews posted for MESOS-4064 addresses MESOS-4113. @hartem,
can you confirm this view?
Reopening this ticket.
@scalp42, It would be great if you check the output from current master is the
same as from 0.26.0. I suspect it is.
> 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)
