Repository files navigation

nginx-proxy sets up a container running nginx anddocker-gen. docker-gen generates reverse proxy configs for nginx and reloads nginx when containers are started and stopped.

SeeAutomated Nginx Reverse Proxy for Docker for why you might want to use this.

To run it:

docker run --detach \    --name nginx-proxy \    --publish 80:80 \    --volume /var/run/docker.sock:/tmp/docker.sock:ro \    nginxproxy/nginx-proxy:1.9

Then start any containers (here an nginx container) you want proxied with an env varVIRTUAL_HOST=subdomain.yourdomain.com

docker run --detach \    --name your-proxied-app \    --env VIRTUAL_HOST=foo.bar.com \    nginx

Provided your DNS is setup to resolvefoo.bar.com to the host running nginx-proxy, a request tohttp://foo.bar.com will then be routed to a container with theVIRTUAL_HOST env var set tofoo.bar.com (in this case, theyour-proxied-app container).

The containers being proxied must :

• expose the port to be proxied, either by using theEXPOSE directive in theirDockerfile or by using the--expose flag todocker run ordocker create.
• share at least one Docker network with the nginx-proxy container: by default, if you don't pass the--net flag when your nginx-proxy container is created, it will only be attached to the default bridge network. This means that it will not be able to connect to containers on networks other than bridge.

Note: providing a port number inVIRTUAL_HOST isn't suported, please seevirtual ports orcustom external HTTP/HTTPS ports depending on what you want to achieve.

The nginx-proxy images are available in two flavors.

This image is based on the nginx:mainline image, itself based on the debian slim image.

docker pull nginxproxy/nginx-proxy:1.9

This image is based on the nginx:alpine image.

docker pull nginxproxy/nginx-proxy:1.9-alpine

Please check thedocs section.