[jira] [Commented] (MESOS-809) External control of the ip that Mesos components publish to zookeeper

["Dimitri (JIRA)" <ji...@apache.org>]

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

Dimitri commented on MESOS-809:
-------------------------------

Sorry for interupting. I am trying hard to make mesos bind to a local interface instead of the public one. 
I have found this thread where it says that binding with env will do the trick.

    LIBPROCESS_ADVERTISE_IP: "10.0.0.3"
    CONSUL_IP:               "10.0.0.3"

I have tried both, but none work. 
I am using mesos with PanteraS, It's a bundled docker image for mesos. I have tried with the env on the host and in the panteras image, none work. could I have some help ?

> External control of the ip that Mesos components publish to zookeeper
> ---------------------------------------------------------------------
>
>                 Key: MESOS-809
>                 URL: https://issues.apache.org/jira/browse/MESOS-809
>             Project: Mesos
>          Issue Type: Improvement
>          Components: framework, master, slave
>    Affects Versions: 0.14.2
>            Reporter: Khalid Goudeaux
>            Assignee: Anindya Sinha
>            Priority: Minor
>             Fix For: 0.24.0
>
>
> With tools like Docker making containers more manageable, it's tempting to use containers for all software installation. The CoreOS project is an example of this.
> When an application is run inside a container it sees a different ip/hostname from the host system running the container. That ip is only valid from inside that host, no other machine can see it.
> From inside a container, the Mesos master and slave publish that private ip to zookeeper and as a result they can't find each other if they're on different machines. The --ip option can't help because the public ip isn't available for binding from within a container.
> Essentially, from inside the container, mesos processes don't know the ip they're available at (they may not know the port either).
> It would be nice to bootstrap the processes with the correct ip for them to publish to zookeeper.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)