You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Kevin Klues (JIRA)" <ji...@apache.org> on 2017/01/18 19:14:26 UTC
[jira] [Commented] (MESOS-6945) Command executor should not see
task's env variables
[ https://issues.apache.org/jira/browse/MESOS-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828596#comment-15828596 ]
Kevin Klues commented on MESOS-6945:
------------------------------------
I believe this has been addressed in master, such that {{mesos-containerizer}} and {{mesos-executor}} inherit the agent ENV and only the task itself inherits the task ENV. [~jieyu] Can you please confirm?
> Command executor should not see task's env variables
> ----------------------------------------------------
>
> Key: MESOS-6945
> URL: https://issues.apache.org/jira/browse/MESOS-6945
> Project: Mesos
> Issue Type: Bug
> Components: executor
> Affects Versions: 1.0.2, 1.1.0
> Reporter: Tomasz Janiszewski
> Priority: Minor
>
> From mailing list [thread|https://lists.apache.org/thread.html/bea58f5b8077ed243e011f13e757cd02ba1ef8a3de9da2ea358193a6@%3Cuser.mesos.apache.org%3E]:
> {quote}
> Hi,
> When I set an environment variable for my task it is as well applied both to mesos-containerizer and mesos-executor.
> This may lead to problems, for example when loading dynamic libraries with LD_PRELOAD.
> Is setting task variables to executor/containerizer a bug?
> Cheers,
> Daniel
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)