> On Jan. 17, 2015, 1:39 a.m., Ben Mahler wrote: > > How are we going to manage the duplication across the command executor and > > the docker executor? > > Timothy Chen wrote: > I think I'm going to leave them seperate as they most likely will grow > independent in tangent. > The docker executor is solely responsible for launching docker > containers, and have different assumptions.
Is there a design doc about this docker architecture decision? It's a bit hard to see the context for this, and how this will play out for other executors that frameworks want to run inside docker, are you planning to support that, or do users have to bake-in their executors..? - Ben ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29329/#review68533 ----------------------------------------------------------- On Jan. 17, 2015, 1:26 a.m., Timothy Chen wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/29329/ > ----------------------------------------------------------- > > (Updated Jan. 17, 2015, 1:26 a.m.) > > > Review request for mesos, Benjamin Hindman and Bernd Mathiske. > > > Repository: mesos > > > Description > ------- > > Add executor for docker containerizer, replaces the usage of command executor > > > Diffs > ----- > > src/Makefile.am 07bea1f > src/docker/executor.cpp PRE-CREATION > > Diff: https://reviews.apache.org/r/29329/diff/ > > > Testing > ------- > > make check > > > Thanks, > > Timothy Chen > >
