[
https://issues.apache.org/jira/browse/MESOS-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jie Yu updated MESOS-4781:
--------------------------
Description: 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.
(was: Currently mesos command executor just inherits all environment variables
from the slave. This could be problematic because when unified containerizer
launches the docker images like mongo or jenkins. Some of the environment
variables are duplicated (such as `PATH` etc.), which causes those docker
images not executing properly. We should prevents those slave environments
exposed to command line executor.)
> 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.4#6332)
