[
https://issues.apache.org/jira/browse/MESOS-6396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576156#comment-15576156
]
Till Toenshoff edited comment on MESOS-6396 at 10/14/16 7:23 PM:
-----------------------------------------------------------------
I wish - unfortunately that one only mutates the Task environment.
see
https://github.com/apache/mesos/blob/master/src/slave/containerizer/docker.cpp#L229,
https://github.com/apache/mesos/blob/master/src/slave/containerizer/docker.cpp#L1060
was (Author: tillt):
I wish - unfortunately that one only mutates the Task environment.
see
https://github.com/apache/mesos/blob/master/src/slave/containerizer/docker.cpp#L229
> Hooks should allow sandbox dependent environment variables.
> -----------------------------------------------------------
>
> Key: MESOS-6396
> URL: https://issues.apache.org/jira/browse/MESOS-6396
> Project: Mesos
> Issue Type: Improvement
> Affects Versions: 1.1.0
> Reporter: Till Toenshoff
> Labels: containerizer, docker, hooks, module
>
> The {{slaveExecutorEnvironmentDecorator}} hook is the only one that allows
> mutating the executor environment of a Docker container. That callback has no
> means of getting the location of the sandbox. That in turn means that it is
> not possible for a hook to create files and respective environment variables
> listing paths within the sandbox for the executor to access.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
