[jira] [Comment Edited] (MESOS-4781) Executor env variables should not be leaked to the command task.

["Jie Yu (JIRA)" <ji...@apache.org>]

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

Jie Yu edited comment on MESOS-4781 at 2/6/17 10:33 PM:
--------------------------------------------------------

One exception maybe MESOS_SANDBOX. Also, we need to consider those task that depends on libprocess (e.g., running framework as a command task). People might already depend on this behavior. We need to have a deprecation cycle for that.


was (Author: jieyu):
One exception maybe MESOS_SANDBOX. Also, we need to consider those task that depends on libprocess (e.g., running framework as a command task).

> Executor env variables should not be leaked to the command task.
> ----------------------------------------------------------------
>
>                 Key: MESOS-4781
>                 URL: https://issues.apache.org/jira/browse/MESOS-4781
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization
>            Reporter: Gilbert Song
>            Assignee: Gilbert Song
>              Labels: mesosphere
>
> Currently, command task inherits the env variables of the command executor. This is less ideal because the command executor environment variables include some Mesos internal env variables like MESOS_XXX and LIBPROCESS_XXX. Also, this behavior does not match what Docker containerizer does. We should construct the env variables from scratch for the command task, rather than relying on inheriting the env variables from the command executor.



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