I’m testing docker 1.12 and as you guys already know : it’s awesome !
The internal DNS to resolve services IP (with round robin, which is fine for simple LB)
But for this to work (e.g. access service app1 from a nginx reverse proxy), a service have to publish a port otherwise the service name can’t be resolved by other services.
I have a nginx reverse proxy with a published port obviously. But I also have to create my services (app1, app2) with published ports so the reverse proxy can work … I don’t know if I miss something, but if, let’s say, app1 exposes port 80, but it’s not publish, when nginx try to proxy the request internally why can’t is resolve app1 IP (with an overlay network private IP for example …) why should I publish service port even when they will never be accessed from outside (only from nginx) …