Re: Use "docker start" rather than "docker run"?

Alex and Marco, Thanks very much for your really helpful explanations. For better or worse, neither cpp nor Python are my things; Java's the go-to language for me. Cordially, Paul On Sat, Aug 29, 2015 at 5:23 AM, Marco Massenzio wrote: > Hi Paul, > > +1 to what Alex/Tim

Re: Use docker start rather than docker run?

Hi Paul, +1 to what Alex/Tim say. Maybe a (simple) example will help: a very basic framework I created recently, does away with the Executor and only uses the Scheduler, sending a CommandInfo structure to Mesos' Agent node to execute. See:

Use docker start rather than docker run?

Hi All, I first posted this to the Marathon list, but someone suggested I try it here. I'm still not sure what component (mesos-master, mesos-slave, marathon) generates the docker run command that launches containers on a slave node. I suppose that it's the framework executor (Marathon) on the

Re: Use docker start rather than docker run?

Alex Tim, Thank you both; most helpful. Alex, can you dispel my confusion on this point: I keep reading that a framework in Mesos (e.g., Marathon) consists of a scheduler and an executor. This reference to executor made me think that Marathon must have *some* kind of presence on the slave node.

Re: Use docker start rather than docker run?

We have primitives for persistent volumes in next release (0.25.0) but DockerContainerizer integration will happen most likely the version after. Tim On Fri, Aug 28, 2015 at 11:50 AM, Tim Chen t...@mesosphere.io wrote: Hi Paul, Alternatively you can try to launch your task on the same host

Re: Use docker start rather than docker run?

Hi Paul, Alternatively you can try to launch your task on the same host by specifying a constraint with marathon and mount a directory on the host in your container everytime to work-around as well. Tim On Fri, Aug 28, 2015 at 11:44 AM, Paul Bell arach...@gmail.com wrote: Alex Tim, Thank

Re: Use docker start rather than docker run?

Heh, that's a tricky one : ). A framework indeed consists of a scheduler and an executor, both are mandatory. But Mesos provides a default general-purpose executor, which can be used by frameworks. This executor has many names, two most common are MesosExecutor and CommandExecutor. Marathon