[MESOS-6323] 'mesos-containerizer launch' should inherit agent environment variables.

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.1.0
• Labels: mesosphere
• Target Version/s: 1.1.0
• Epic Link: Environment Variables
• Sprint: Mesosphere Sprint 44
• Story Points: 5
• Assignee: Jie Yu
• Reporter: Jie Yu
• Created: 07/Oct/16 00:54
• Updated: 16/Sep/17 11:37
• Resolved: 12/Oct/16 00:00

Description

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.

Issue Links

• breaks: MESOS-7958 The example framework `test-framework` is broken.
• is duplicated by: MESOS-6337 Nested containers getting killed before network isolation can be applied to them.