[jira] [Commented] (MESOS-7405) Allow isolators to render mapped sandbox specific environment variables.

["Till Toenshoff (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975694#comment-15975694 ] 

Till Toenshoff commented on MESOS-7405:
---------------------------------------

The hook {{slavePreLaunchDockerTaskExecutorDecorator}} does allow just that when using the docker-containerizer, hence I am suggesting this missing feature in the mesos-containerizer to be regarded as a bug.

> Allow isolators to render mapped sandbox specific environment variables.
> ------------------------------------------------------------------------
>
>                 Key: MESOS-7405
>                 URL: https://issues.apache.org/jira/browse/MESOS-7405
>             Project: Mesos
>          Issue Type: Bug
>          Components: agent, containerization, isolation
>            Reporter: Till Toenshoff
>
> Within the mesos-containerizer, isolators are responsible for preparing the containerized context for an executor by implementing [{{prepare}}|https://github.com/apache/mesos/blob/253c89483cb6e31225a1f55449ff88c676030eec/include/mesos/slave/isolator.hpp#L68-L70].
> Part of such preparation may e.g. be sandbox mutations within the root filesystem as well as rendering environment variables returned via the optionally returned [{{ContainerLaunchInfo}}|https://github.com/apache/mesos/blob/253c89483cb6e31225a1f55449ff88c676030eec/include/mesos/slave/containerizer.proto#L164].
> IIUC currently it seems to not be possible to have an isolator setup environment variables pointing to mapped locations within the sandbox path as that path gets determined after all isolators did their preparation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)