Hi Javier, Like Ryan said the network mode is not configurable at the moment, I'm planning to add bridge network and port mappings next.
Thanks, Tim On Thu, Aug 28, 2014 at 3:51 PM, Ryan Thomas <[email protected]> wrote: > I believe that the docker containerizer in mesos is hard coded to use > host-based networking at the moment. i.e. the --net=host flag. > > This means that the ports the container binds to internally will be on the > slaves interface and exposed. > On 29 Aug 2014 08:45, "Javier Ruiz Jiménez" <[email protected]> wrote: > >> Hi All >> >> I am translating all our Marathon API calls to new format for Marathon 0 >> .7.0-SNAPSHOT as we have upgraded to Mesos 0.20.0. >> >> I used to map some container ports to well known host ports. >> >> Example from when using Deimos: >> >> "options" : ["-p","9000:9000"] >> >> Following Marathon upgrade guide in >> https://mesosphere.github.io/marathon/docs/upgrade/06xto070.html >> >> { >> "container": { >> "image": "docker:///megacorp/product:1.2.3", >> "options": [ >> "-v", "/var/data/a:/etc/a:ro", >> "-v", "/var/data/b:/etc/b:rw", >> "-e", "FOO=bar", >> "-p", "443:443" >> ] >> } >> } >> >> Gets translated to: >> >> { >> "container": { >> "type": "DOCKER", >> "docker": { >> "image": "megacorp/product:1.2.3" >> }, >> "volumes": [ >> { >> "hostPath": "/var/data/a", >> "containerPath": "/etc/a", >> "mode": "RO" >> }, >> { >> "hostPath": "/var/data/b", >> "containerPath": "/etc/b", >> "mode": "RW" >> } >> ] >> }, >> "env": { >> "FOO": "bar" >> }, >> "ports": [443], >> "requirePorts": true >> } >> >> But if I do the same, docker ps shows no port mappings for the container. >> No ports are mapped. >> >> Any suggestions? >> How can I see the "docker run command " that mesos executes? >> >> Thanks, >> Javier >> >>
