[jira] [Commented] (MESOS-2587) libprocess should allow configuration of ip/port separate from the ones it binds to

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

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

Dimitri commented on MESOS-2587:
--------------------------------

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 ?

> libprocess should allow configuration of ip/port separate from the ones it binds to
> -----------------------------------------------------------------------------------
>
>                 Key: MESOS-2587
>                 URL: https://issues.apache.org/jira/browse/MESOS-2587
>             Project: Mesos
>          Issue Type: Bug
>          Components: libprocess
>            Reporter: Cosmin Lehene
>
> Currently libprocess will advertise {{LIBPROCESS_IP}}{{LIBPROCESS_PORT}}, but if a framework runs in a container without an an interface that has a publicly accessible IP (e.g. a container in bridge mode) it will advertise an IP that will not be reachable by master.
> With this, we could advertise the external IP (reachable from master) of the bridge from within a container. 
> This should allow frameworks running in containers to work in the safer bridged mode.



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