Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Thu, 13 Oct 2016 16:00:27 +0000 (UTC)
From: "Jie Yu (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.13010333.1475801685000.818404.1476374427366@Atlassian.JIRA>
In-Reply-To: <JIRA.13010333.1475801685000@Atlassian.JIRA>
References: <JIRA.13010333.1475801685000@Atlassian.JIRA> <JIRA.13010333.1475801685891@arcas>
Subject: [jira] [Updated] (MESOS-6323) 'mesos-containerizer launch' should
 inherit agent environment variables.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 13 Oct 2016 16:00:29 -0000


     [ https://issues.apache.org/jira/browse/MESOS-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jie Yu updated MESOS-6323:
--------------------------
    Story Points: 5

> 'mesos-containerizer launch' should inherit agent environment variables.
> ------------------------------------------------------------------------
>
>                 Key: MESOS-6323
>                 URL: https://issues.apache.org/jira/browse/MESOS-6323
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Jie Yu
>            Assignee: Jie Yu
>            Priority: Critical
>              Labels: mesosphere
>             Fix For: 1.1.0
>
>
> If some dynamic libraries that agent depends on are stored in a non standard location, and the operator starts the agent using LD_LIBRARY_PATH. When we actually fork/exec the 'mesos-containerizer launch' helper, we need to make sure it inherits agent's environment variables. Otherwise, it might throw linking errors. This makes sense because it's a Mesos controlled process.
> However, the the helper actually fork/exec the user container (or executor), we need to make sure to strip the agent environment variables.
> The tricky case is for default executor and command executor. These two are controlled by Mesos as well, we also want them to have agent environment variables. We need to somehow distinguish this from custom executor case.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)