[
https://issues.apache.org/jira/browse/MESOS-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083169#comment-14083169
]
Timothy Chen commented on MESOS-1659:
-------------------------------------
[~jaybuff] as [~vinodkone] and [~dhamon] mentioned it is quite complicated and
honestly I think beats the purpose of docker that is suppose to bring in all
the dependencies for you. Also the dependencies are actually quite huge and
there are number of them, and not every task with docker image requires this. I
think we shouldn't do this that is very error prone, and leave this to the
person having the right docker image to include all the dependencies for
running your image. Alternatively you can yourself provide the dependencies for
the docker image yourself want to use in the CommandInfo URI and we will volume
mount it into your docker image that you can find yourself.
> docker containerizer should not require executor be part of image
> -----------------------------------------------------------------
>
> Key: MESOS-1659
> URL: https://issues.apache.org/jira/browse/MESOS-1659
> Project: Mesos
> Issue Type: Improvement
> Reporter: Jay Buffington
>
> I would like the ability to run an executor inside of an off-the-shelf docker
> container.
> We already have a process for getting an executor into the sandbox. I've
> spoken with [~tnachen] about this and we agreed that the containerize should
> bind mount (via the docker volumes feature) the sandbox into the container
> and run the executor.
> The problem with this is the majority of executors have a dependency on
> libmesos and libmesos usually doesn't exist in off the shelf containers.
> I propose the docker containerize also bind mount libmesos and it's
> dependencies (like libunwind) into the container and use LD_LIBRARY_PATH so
> the executor can find them.
> You could make an argument that executors should be statically compiled self
> contained binaries, but that is difficult with executors written in python or
> java. We can use pex or jar to package up language dependencies, but native
> deps like libmesos are tricky. Having the docker containerize guarantee that
> libmesos is there really simplifies things.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
