From 9b0138f9440c4ff218b2e0d9c84e5ef7c1039d4c Mon Sep 17 00:00:00 2001 From: Jason Wilder Date: Fri, 10 Jun 2016 20:11:58 -0600 Subject: [PATCH] Remove docker compose v2 notes --- README.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/README.md b/README.md index f917ea6..9e049fe 100644 --- a/README.md +++ b/README.md @@ -19,11 +19,6 @@ The containers being proxied must [expose](https://docs.docker.com/reference/run Provided your DNS is setup to forward foo.bar.com to the a host running nginx-proxy, the request will be routed to a container with the VIRTUAL_HOST env var set. -### Docker-compose - -Currently this does not work with the new v2 syntax of docker-compose (due to not being compatible with the new network overlay see [#304](https://github.com/jwilder/nginx-proxy/issues/304)). It does work when using the old docker-composer syntax. - - ### Multiple Ports If your container exposes multiple ports, nginx-proxy will default to the service running on port 80. If you need to specify a different port, you can set a VIRTUAL_PORT env var to select a different one. If your container only exposes one port and it has a VIRTUAL_HOST env var set, that port will be selected.