[
https://issues.apache.org/jira/browse/MESOS-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069125#comment-15069125
]
Anthony Scalisi commented on MESOS-4113:
----------------------------------------
[~hartem] and [~bernd-mesos], is the Docker internal ip going to be exposed as
in 0.26.0 ? I'm trying to figure if it's still going to be broken in 0.27.0 as
this JIRA issue was marked as resolved but it does not give a lot of confidence
the issue was understood.
Here is output of Marathon with Mesos v0.25.0 (please note the empty array for
IpAddresses):
!https://camo.githubusercontent.com/82c8a341b355d89d40cacf730dc4e3cfbe7001a9/68747470733a2f2f692e696d6775722e636f6d2f4365715131516b2e706e67!
And here is the output with Mesos v0.26.0 (broken, please note the ip of the
Docker container not reachable):
!https://camo.githubusercontent.com/42b5c998084182dc3f9c4b090256ce2d71b96b1f/68747470733a2f2f692e696d6775722e636f6d2f706d32636b62352e706e67!
> 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)
