iirc i just used netstat from a dash script (in the docker container) to get the gateway address, or used containers with --net=host, as appropriate
:c On 24 Jan 2015, at 20:58, Gallagher Polyn <[email protected]> wrote: On Thu, Jan 22, 2015 at 1:05 PM, craig mcmillan <[email protected]> wrote: > we use the HAProxy configurator script bundled with marathon to bind > applications to ports : > > https://github.com/mesosphere/marathon/blob/master/bin/ > haproxy-marathon-bridge > > HAProxy runs on every mesos slave and each marathon app is then available > on every slave at the port(s) declared in the marathon API on localhost (or > the docker container gateway host) > > Given the foregoing, can mesos-dns + mesos (possibly, mesosphere’s >> marathon) + docker be configured to emulate Kubernetes’ style of service >> discovery, i.e., no responsibility for DNS resolution in an application >> consuming other services via TCP? >> > Craig, I now see at least advantage for mesos-dns in the context you introduced in your comment: responsibilities for configuring a standard docker container gateway host or handling the docker container gateway host's resolution in client code can be replaced by mesos-dns. Maybe no big deal, especially if you recommend an easy approach to making the docker container gateway host visible. G
