[ https://issues.apache.org/jira/browse/MESOS-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569941#comment-15569941 ]
Joseph Wu commented on MESOS-6323: ---------------------------------- {code} commit 8c8ec608503394575a4f99fd725010b8920e5efa Author: Joseph Wu <josep...@apache.org> Date: Wed Oct 12 11:57:18 2016 -0700 Windows: Implemented os::execvpe with _spawnvpe. Review: https://reviews.apache.org/r/52798 {code} > '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 > 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)