You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org> on 2015/12/04 22:29:11 UTC

[jira] [Commented] (MESOS-3740) LIBPROCESS_IP not passed to Docker containers

    [ https://issues.apache.org/jira/browse/MESOS-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042259#comment-15042259 ] 

Niklas Quarfot Nielsen commented on MESOS-3740:
-----------------------------------------------

[~tnachen] Sorry for the radio silence. Do you have capacity to take this on/shepherding?

> 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
>              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)