[MESOS-3740] LIBPROCESS_IP not passed to Docker containers

• Type: Bug
• Status: Accepted
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.25.0
• Component/s: containerization, docker
• Labels: mesosphere

Environment

Mesos 0.24.1

• Epic Link: Environment Variables
• Sprint: Mesosphere Sprint 21
• Assignee: Unassigned
• Reporter: Cody Maloney
• Created: 14/Oct/15 23:58
• Updated: 26/Nov/18 13:36

Description

Docker containers aren't currently passed all the same environment variables that Mesos Containerizer tasks are. See: https://github.com/apache/mesos/blob/master/src/slave/containerizer/containerizer.cpp#L254 for all the environment variables explicitly set for mesos containers.

While some of them don't necessarily make sense for docker containers, when the docker has inside of it a libprocess process (A mesos framework scheduler) and is using --net=host the task needs to have LIBPROCESS_IP set otherwise the same sort of problems that happen because of MESOS-3553 can happen (libprocess will try to guess the machine's IP address with likely bad results in a number of operating environment).

Issue Links

• is related to: MESOS-3553 LIBPROCESS_IP not passed when executor's environment is specified