[ https://issues.apache.org/jira/browse/MESOS-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994487#comment-14994487 ]
Timothy Chen commented on MESOS-3740: ------------------------------------- Alternatively is to have a list of enviornment variables that we should include, except explicit values. Regardless I'm not really thinking that regex or prefixes is a good way to go. > LIBPROCESS_IP not passed to Docker containers > --------------------------------------------- > > Key: MESOS-3740 > URL: https://issues.apache.org/jira/browse/MESOS-3740 > Project: Mesos > Issue Type: Bug > Components: containerization, docker > Affects Versions: 0.25.0 > Environment: Mesos 0.24.1 > Reporter: Cody Maloney > Assignee: Michael Park > Labels: mesosphere > > 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). -- This message was sent by Atlassian JIRA (v6.3.4#6332)