Based on https://github.com/jwilder/nginx-proxy
A new env varaible ENABLE_ACME is added to use acme.sh to generate free ssl cert from letsencrypt.
All the other options are the same as the upstream project: https://github.com/jwilder/nginx-proxy
It's very easy to use:
docker run \
-p 80:80 \
-p 443:443 \
-it -d --rm \
-v /var/run/docker.sock:/tmp/docker.sock:ro \
-v $(pwd)/proxy/certs:/etc/nginx/certs \
-v $(pwd)/proxy/acme:/acmecerts \
-v $(pwd)/proxy/conf.d:/etc/nginx/conf.d \
-v $(pwd)/vhost.d:/etc/nginx/vhost.d \
-v $(pwd)/stream.d:/etc/nginx/stream.d \
-v $(pwd)/dhparam:/etc/nginx/dhparam \
--name proxy \
neilpang/nginx-proxy
It's recommended to run with --net=host option, like:
docker run \
-it -d --rm \
-v /var/run/docker.sock:/tmp/docker.sock:ro \
-v $(pwd)/proxy/certs:/etc/nginx/certs \
-v $(pwd)/proxy/acme:/acmecerts \
-v $(pwd)/proxy/conf.d:/etc/nginx/conf.d \
-v $(pwd)/vhost.d:/etc/nginx/vhost.d \
-v $(pwd)/stream.d:/etc/nginx/stream.d \
-v $(pwd)/dhparam:/etc/nginx/dhparam \
--name proxy \
--net=host \
neilpang/nginx-proxy
For a docker compose v2 or v3 project, every project has a dedicated network, so, you must use --net=host option, so that it can proxy any projects on you machine.
version: '2'
services:
nginx-proxy:
image: neilpang/nginx-proxy
ports:
- "80:80"
- "443:443"
volumes:
- /var/run/docker.sock:/tmp/docker.sock:ro
- ./proxy/certs:/etc/nginx/certs
- ./proxy/acme:/acmecerts
- ./proxy/conf.d:/etc/nginx/conf.d
- ./proxy/vhost.d:/etc/nginx/vhost.d \
- ./proxy/stream.d:/etc/nginx/stream.d \
- ./proxy/dhparam:/etc/nginx/dhparam \
network_mode: "host"
docker run -itd --rm \
-e VIRTUAL_HOST=foo.bar.com \
-e ENABLE_ACME=true \
httpd
Content type
Image
Digest
Size
58.4 MB
Last updated
about 7 years ago
docker pull zhaishuaigan/nginx-proxy