Hi Karan, Before figuring out some ways to achieve this with Mesos, I would like to better understand your use cases.
Do you mean you rely on `docker attach/exec` to send commands to an existing running container? Is there any reason that keeps you from launching a container for each batch job? Gilbert On Wed, Mar 21, 2018 at 10:29 AM, karanprad...@gmail.com < karanprad...@gmail.com> 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 >
