[ https://issues.apache.org/jira/browse/MESOS-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998930#comment-14998930 ]
Anindya Sinha commented on MESOS-2587: -------------------------------------- Please refer to MESOS-809 for a followup to this. > 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)