Just noticed that my comments below were also raised on the MESOS-816 issue… it concerns me a little that there would be a requirement for the container to have all the mesos libs/the executor files installed. Though I don’t see any easy alternatives.
I’ll continue my development with the assumption that a container has everything required already in the filesystem. — Tom Arnfeld Developer // DueDil On 11 Feb 2014, at 09:07, Tom Arnfeld <[email protected]> wrote: > Hey > > I posted this on IRC but I don’t think anyone was around… I've started to > implement a crude docker isolator (until MESOS-816 is finished) and come up > against a wall. The ExecutorLauncher class is usually responsible for setting > up the environment/invoking the mesos-launcher script, however when inside a > docker container none of these files exist. > > I'm in two minds, whether to do something crazy and mount the relevant > directories as volumes within the container (so the container can access the > mesos lib/launcher script etc) or to require that the docker image contains > all of these things.. and the executor for the specific mesos task and any > other files that are in the sandbox.. > > The mounting option requires that the container has all of the required > dependencies installed to run mesos… i’m leaning towards requiring the > container to include everything for the task, including the executor. Though > it *is* possible to inject files into the container filesystem so it’d be an > added bonus if files from the sandbox (jars etc) could be put into the > container to make docker images a little more re-usable across different > frameworks. > > Any thoughts on my direction would be very much appreciated. > > — > > Tom Arnfeld > Developer // DueDil >
