Hi Michael, Can you elaborate how you use the Mesos containerizer to you prepare your host?
In general hooks are exactly for this purpose, which is underway right now for defining the hooks in Mesos and also allowing it to be customized. Tim On Thu, Feb 19, 2015 at 6:18 PM, Michael Neale <[email protected]> wrote: > I am currently using marathon and have a need to "prepare" the host in > some cases (currently looking at mounting a volume that the task may need - > how that device is created is out of band BTW). > > In theory this would be ideally done on some hook - but I am not sure > where (the hook would be called before the task proper is launched) - it > could be simply as part of a task launch script if a plain command. > > With the docker containerizer - I can actually use priv mode and control > the host (if I want) - but then I would like to have this task run > separately to the main marathon long running task (as it has extra access > which normally apps don't need) - I could bind mount in the docker socket > and launch a non priv container from within the mesos launched start > container ... > > I can also use the default (?) mesos containerizer - which seems to let me > run docker commands (ie bypassing the firstclass support in mesos for > docker) but this "feels" like I am doing it wrong - is that wrong? > > So in summary: is there a concept of a pre-launch step, and should I be > working around the docker containerizer by using the mesos default > containerizer instead? > > pointers appreciated. >
