[
https://issues.apache.org/jira/browse/MESOS-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14984461#comment-14984461
]
Cody Maloney commented on MESOS-3740:
-------------------------------------
When this came up was trying to launch a mesos framework inside of a docker
container. The framework used libmesos, and that libmesos couldn't figure out
what IP to use (the machine didn't have a hostname, and even if it did, the
hostname may not resolve to the right IP address the mesos framework inside the
docker container should announce as its own IP, due to something like having
multiple addresses on the machine, or running in an IP per container type
environment)
> 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)
