Hi Tom, Docker cgroup parenting recently landed, so recovering from such a tricky situation may no longer be as difficult if docker containers are parented to the executor's cgroup at run-time.
On Tue, Apr 7, 2015 at 7:15 PM, Tom Arnfeld <t...@duedil.com> wrote: > It's not possible to invoke the docker containerizer from outside of > Mesos, as far as I know. > > If you persue this route, you can run into issues with orphaned containers > as your executor may die for some unknown reason, and the container is > still running. Recovering from this can be tricky business, so it's better > if you can adapt your framework design to fit within the Mesos > Task/Executor pattern. > > -- > > Tom Arnfeld > Developer // DueDil > > (+44) 7525940046 > 25 Christopher Street, London, EC2A 2BS > > > On Mon, Apr 6, 2015 at 7:00 PM, Vinod Kone <vinodk...@apache.org> wrote: > >> Tim, do you want answer this? >> >> On Wed, Apr 1, 2015 at 7:27 AM, Tom Fordon <tom.for...@gmail.com> wrote: >> >>> Hi. I'm trying to understand using docker within a custom executor. For >>> each of my tasks, I would like to perform some steps on the node before >>> launching a docker container. I was planning on writing a custom python >>> executor for this, but I wasn't sure how to launch docker from within this >>> executor. >>> >>> Can I just call docker in a subprocess using the ContainerInfo from the >>> Task? If I do this, how does the Containerizer fit in? >>> Thank you, >>> Tom Fordon >>> >> >> > -- James DeFelice 585.241.9488 (voice) 650.649.6071 (fax)
