Re: Incompleteness of ContainerInfo.DockerInfo.DockerInfo ?

Thank you On Tue, Dec 22, 2015 at 5:11 AM, Adam Bordelon wrote: > 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

Re: Incompleteness of ContainerInfo.DockerInfo.DockerInfo ?

Hello, Apparently Marathon does not support portMapping with host IP address either. Fragment from https://mesosphere.github.io/marathon/docs/rest-api.html#post-v2-apps "portMappings": [ { "containerPort": 8080, "hostPort": 0,

Re: Incompleteness of ContainerInfo.DockerInfo.DockerInfo ?

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

Re: Incompleteness of ContainerInfo.DockerInfo.DockerInfo ?

see marathon implementation? 2015-12-19 22:49 GMT+08:00 Viktor Sadovnikov : > Hi, > > Do I understand correctly that currently > ContainerInfo.DockerInfo.DockerInfo of > Mesos Proto ( > >

Incompleteness of ContainerInfo.DockerInfo.DockerInfo ?

Hi, Do I understand correctly that currently ContainerInfo.DockerInfo.DockerInfo of Mesos Proto ( https://github.com/apache/mesos/blob/f9f379ddc315fb07e9862238dbe6e83988ac66c6/include/mesos/mesos.proto) lacks IP address field in order to support ip:hostPort:containerPort format of port mappings,