[
https://issues.apache.org/jira/browse/MESOS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589813#comment-14589813
]
Benjamin Hindman commented on MESOS-2832:
-----------------------------------------
This should be pretty straightforward. As an MVP I propose adding a boolean
'strip_environment_variables' flag to the slave. If people feel strongly about
it we could also make this a string flag where '*' means all environment
variables (except the ones we explicitly add) or it can represent an explicit
list of which environment variables to strip.
To do this most cleanly in the code we'll need to update process::subprocess to
use the passed in environment as a replacement rather than a "merge". This is a
more straightforward API anyway, and captures a long-standing TODO in the code.
> Enable configuring Mesos with environment variables without having them leak
> to tasks launched
> ----------------------------------------------------------------------------------------------
>
> Key: MESOS-2832
> URL: https://issues.apache.org/jira/browse/MESOS-2832
> Project: Mesos
> Issue Type: Wish
> Reporter: Cody Maloney
> Priority: Critical
> Labels: mesosphere
>
> Currently if mesos is configured with environment variables (MESOS_MODULES),
> those show up in every task which is launched unless the executor explicitly
> cleans them up.
> If the task being launched happens to be something libprocess / mesos based,
> this can often prevent the task from starting up (A scheduler has issues
> loading a module intended for the slave).
> There are also cases where it would be nice to be able to change what the
> PATH is that tasks launch with (the host may have more in the path than tasks
> are supposed to / allowed to depend upon).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
