[
https://issues.apache.org/jira/browse/MESOS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14590499#comment-14590499
]
Cody Maloney commented on MESOS-2832:
-------------------------------------
For DCOS at least we don't want to just strip some out. We want to replace the
entire environment with one statically spaecified. The reason for this is we
explicitly want to make it hard to depend on special DCOS-internal components
that mesos-slave has in it's PATH, LD_LIBRARY_PATH but which DCOS Services
should not.
Removing a magic pattern matching of variables seems more complicated to
implement than "Load the exact set of environment variables to use from this
map, then add in explicitly Mesos API provided ones, such as MESOS_SANDBOX, etc"
> 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
> Assignee: Benjamin Hindman
> 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)
