On 2018/03/21 17:51:58, Harold Dost <[email protected]> wrote: > What gain are you looking to get from having the singular container. If you > desire a shared context you could consider listening on a port and sending > them over http. Otherwise I would say just launch each of your tasks > separately. > > ________________________________________ > > Harold Dost | @hdost > > > > On Wed, Mar 21, 2018, 18:29 [email protected] <[email protected]> > wrote: > > > Hi, > > > > I was docker for running my batch job in which I would follow this > > approach: > > > > 1. Start the docker container > > 2. Send commands to the running Docker container with the help of docker > > python client for each batch of objects. > > 3. After all the batches are processed by the docker, shut down the > > container. > > > > I wanted to achieve the same with the help of Mesos and Marathon to spin > > up containers and submit commands per batch. > > But looking a the documents it looks like that this behavior is not > > achievable as when Mesos spin up a Docker container with the help of Mesos > > containerizer and docker/runtime isolation you can submit only one command > > after which the Sesos framework is killed. > > > > It would be great if someone could point me to a way to achieve this using > > Mesos containerizer? > > > > Thanks, > > Karan > > > Hi Harold, Thanks for taking time answering my question.
There is no particular reason why we don't run new docker. Would that add overhead if I had multiple batches which need to be processed? Also, I have a constraint that the docker must run on a particular host for all the batches I have. Thanks, Karan
