[
https://issues.apache.org/jira/browse/MESOS-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994319#comment-14994319
]
Cody Maloney commented on MESOS-3740:
-------------------------------------
The {{--executor-environment-variables}} is given directly to executors, and
then gets inherited from the executor by all tasks the executors launch
currently. We can't do just one generic flag of
{{--docker-task-environment-variables}} which includes LIBPROCESS_IP, because
LIBPROCESS_IP is something that Mesos can / will calculate (Either using it's
classic reverse lookup behavior or --ip-detect-script). So that one I think
still needs to be special cased that we always just pass it through to solve
the current present problem.
Adding a {{--docker-environment-variables}} which applies to all exectors and
tasks launched with the docker containerizer could be useful in some
circumstances (although within DCOS we have no need to pass special / extra /
explicit environment variables to docker containers). The
{{--docker-environment-variables}} still wouldn't be able to capture
LIBPROCESS_IP though.
> 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)
