[
https://issues.apache.org/jira/browse/MESOS-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072962#comment-15072962
]
Gastón Kleiman commented on MESOS-4113:
---------------------------------------
When creating a task, Marathon associates a "ports array" to it. That array
contains the ports requested in the TaskInfo message passed to Mesos through
the launchTasks API call. If the task uses Docker port-mappings, then the host
ports are used.
When the Marathon user defines a health check, he has to specify a an index
("portIndex") into the ports array. That index will then be used by Marathon to
get the effective port number.
Marathon v0.14.0-RC1 allows the user to supply a "hard-coded" port number
instead of a port index.
> 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)
