I managed to resolve this thanks to code completion hints in my IDE. I needed to configure bridge networking:
dockerInfoBuilder.setNetwork(Protos.ContainerInfo.DockerInfo.Network.BRIDGE); I'd recommend adding this to the documentation as most people will probably expect this to be the default behavior. I'd also be happy to contribute this example code to be shipped with Mesos if there's any interest in that. Thanks, Andy. -- Andy Grove VP Engineering CodeFutures Corporation On Wed, Oct 1, 2014 at 1:47 PM, Andy Grove <andy.gr...@codefutures.com> wrote: > Hi, > > I'm making better progress but have run into another issue that I need > help tracking down. > > I've actually packaged up my code in a github repo now and will be writing > up a tutorial on this once I have everything working. > > https://github.com/codefutures/mesos-docker-tutorial > > The README.md contains instructions on running the framework. > > I can use this to start a single instance of the fedora/apache container > but when I try and run multiple instances the first one works but the other > containers start and then fail pretty quickly. > > I tracked down the error information in the sandbox and the other > containers are failing with "cannot bind to port 80" so it looks like the > containers are being launched with host networking (-net=host). I thought > this was one of the issues that was fixed in 0.20.1. Do I have to do > something to enable containerized networking? > > Thanks, > > Andy. > > -- > Andy Grove > VP Engineering > CodeFutures Corporation > > >
