Doesn't seem to work with new docker networking

[blackxored]

It doesn't seem to work with the new docker networking features. i.e. --x-networking for example on docker compose. I'm not really sure if it should to begin with, but it would be handy.
I'm running a SPA, API and DB under a new networked setup and nginx-proxy gives a 503 even when the LB has the VIRTUAL_HOST env var. Are you aware of this?

[thaJeztah]

possible duplicate of #304?

[blackxored]

It might be. The only difference is that I'm talking local networking, but yes the lacking support for the new networking API definitely seems like the culprit.

[modius]

👍

Trying to move from links to networking (available in Docker 1.9+) and this definitely appears to be an issue.

While links are still supported in this limited capacity, you should avoid them in preference of Docker networks. The link feature is expected to be deprecated and removed in a future release.

https://docs.docker.com/engine/userguide/networking/dockernetworks/

[modius]

@schmunk42 did this commit make it into the Docker image?

nginx-proxy/docker-gen@fdf2922

[md5]

@modius No. But see nginx-proxy/docker-gen#144

[tkw1536]

Related issue is closed, closing.