[
https://issues.apache.org/jira/browse/MESOS-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069120#comment-15069120
]
Anthony Scalisi commented on MESOS-4113:
----------------------------------------
I opened https://github.com/mesosphere/marathon/issues/2870 but it appears to
be a Mesos issue.
I can confirm on v0.26.0, all our health checks in Marathon stopped working as
the ip returned is the internal docker one which is not accessible from the
host itself.
We downgraded to v0.25.0 and all health checks are passing now.
Could someone explain if the issue is actually resolved in 0.27.0 ? It's not
clear if it is.
Thanks in advance!
> 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)
