[
https://issues.apache.org/jira/browse/MESOS-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15979248#comment-15979248
]
Till Toenshoff commented on MESOS-7405:
---------------------------------------
[~jieyu] and I had a chat around this issue. We agreed that allowing the
isolator to receive the mapped sandbox path via {{ContainerConfig}} in
{{prepare}} would be a solution for this problem.
> 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)
