zombi
/
nginx-proxy
Archived
11
0
Fork 0
Code Issues Pull Requests Releases Activity

Merge pull request #371 from gabriel403/patch-1 

Mention the docker-compose networking issues
This commit is contained in:
Jason Wilder 2016-03-03 15:35:43 -07:00
parent 2b24c1712a d849e5f5d0
commit 87d0c68aac
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -18,6 +18,11 @@ 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.