[
https://issues.apache.org/jira/browse/MESOS-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067731#comment-15067731
]
Viktor Sadovnikov commented on MESOS-4215:
------------------------------------------
received from Adam Bordelon on [email protected]
{quote}
Viktor, you are correct that Mesos' DockerInfo doesn't have explicit support
for the ip:hostPort:containerPort format, but you can use the
DockerInfo.parameters field to pass arbitrary parameters to the docker CLI.
https://github.com/apache/mesos/blob/0.26.0/include/mesos/mesos.proto#L1482
"parameters": "-p 192.168.99.100:8080:8080/tcp"
{quote}
> IP address in PortMapping
> -------------------------
>
> Key: MESOS-4215
> URL: https://issues.apache.org/jira/browse/MESOS-4215
> Project: Mesos
> Issue Type: Bug
> Reporter: Viktor Sadovnikov
>
> Looking at {{include/mesos/mesos.proto}}
> {noformat}
> message PortMapping {
> required uint32 host_port = 1;
> required uint32 container_port = 2;
> // Protocol to expose as (ie: tcp, udp).
> optional string protocol = 3;
> }
> {noformat}
> {{ContainerInfo.DockerInfo.DockerInfo}} seems to be lacking host IP-address,
> which can be used to in {{ip:hostPort:containerPort}} format of mapping in
> {{docker run}} command.
> Currently, if my host has several IP addresses, setting up mapping on a port
> (for example, 8080) for one container blocks results in
> {{0.0.0.0:8080->8080/tcp}} and this blocks creation of other containers with
> mapping on the same port (but different IP address). My expectation is that
> specifying IP address will result in something like
> {{192.168.99.100:8080->8080/tcp}} and this will not block creation of other
> containers
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
