[
https://issues.apache.org/jira/browse/MESOS-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051713#comment-15051713
]
Vinod Kone commented on MESOS-4090:
-----------------------------------
One thing I had in mind was that we could do something similar to generate a
stripped down version of the egg.
Also, not sure how this approach plays with our previous split of mesos egg
into native, interface etc eggs.
[~tillt] [~wickman] [~thomasr] Comments on the above review/approach?
> Create a light-weight, executor only mesos egg
> ----------------------------------------------
>
> Key: MESOS-4090
> URL: https://issues.apache.org/jira/browse/MESOS-4090
> Project: Mesos
> Issue Type: Improvement
> Components: build
> Reporter: Steve Niemitz
> Assignee: Steve Niemitz
>
> Currently, when running tasks in docker containers, if the executor uses the
> mesos.native python library, the execution environment inside the container
> (OS, native libs, etc) must match the execution environment outside the
> container fairly closely in order to load the mesos.so library.
> The solution here can be to introduce a much lighter weight python egg,
> mesos.executor, which only includes code (and dependencies) needed to create
> and run an MesosExecutorDriver. Executors can then use this native library
> instead of mesos.native.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
