mirror of
https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion
synced 2024-04-18 23:33:53 +02:00
docs: jwilder/docker-gen -> nginxproxy/docker-gen
This commit is contained in:
parent
b7e1362115
commit
027c3cf3bf
|
@ -1,6 +1,6 @@
|
|||
## Advanced usage (with the nginx and docker-gen containers)
|
||||
|
||||
**nginx-proxy** can also be run as two separate containers using the [jwilder/**docker-gen**](https://github.com/jwilder/docker-gen) image and the official [**nginx**](https://hub.docker.com/_/nginx/) image. You may want to do this to prevent having the docker socket bound to a publicly exposed container service (ie avoid mounting the docker socket in the nginx exposed container).
|
||||
**nginx-proxy** can also be run as two separate containers using the [nginx-proxy/**docker-gen**](https://github.com/nginx-proxy/docker-gen) image and the official [**nginx**](https://hub.docker.com/_/nginx/) image. You may want to do this to prevent having the docker socket bound to a publicly exposed container service (ie avoid mounting the docker socket in the nginx exposed container).
|
||||
|
||||
**NOTE**: The first time this container is launched in a three container setup, it will generates a new 2048 bits Diffie-Hellman parameters file. This process can take up to several minutes to complete on lower end hosts, and certificates creation won't start before that (be patient).
|
||||
|
||||
|
@ -44,7 +44,7 @@ $ docker run --detach \
|
|||
--volumes-from nginx-proxy \
|
||||
--volume /path/to/nginx.tmpl:/etc/docker-gen/templates/nginx.tmpl:ro \
|
||||
--volume /var/run/docker.sock:/tmp/docker.sock:ro \
|
||||
jwilder/docker-gen \
|
||||
nginxproxy/docker-gen \
|
||||
-notify-sighup nginx-proxy -watch -wait 5s:30s /etc/docker-gen/templates/nginx.tmpl /etc/nginx/conf.d/default.conf
|
||||
```
|
||||
|
||||
|
|
|
@ -75,7 +75,7 @@ services:
|
|||
network_mode: bridge
|
||||
|
||||
docker-gen:
|
||||
image: jwilder/docker-gen
|
||||
image: nginxproxy/docker-gen
|
||||
container_name: nginx-proxy-gen
|
||||
command: -notify-sighup nginx-proxy -watch /etc/docker-gen/templates/nginx.tmpl /etc/nginx/conf.d/default.conf
|
||||
volumes_from:
|
||||
|
|
|
@ -18,7 +18,7 @@ And two methods to inform the **acme-companion** container of the **docker-gen**
|
|||
|
||||
The methods for each container are sorted by order of precedence, meaning that if you use both the label and the volumes_from method, the ID of the **nginx**/**nginx-proxy** container that will be used will be the one found using the label. **There is no point in using more than one method at a time for either the nginx/nginx-proxy or docker-gen container beside potentially confusing yourself**.
|
||||
|
||||
The advantage the `label` methods have over the `environment variable` (and `volumes_from`) methods is enabling the use of the **acme-companion** in environments where containers names are dynamic, like in Swarm Mode or in Docker Cloud. Howhever if you intend to do so, as upstream **docker-gen** lacks the ability to identify containers from labels, you'll need both to either use the two containers setup or to replace jwilder/docker-gen with a fork that has this ability like [herlderco/docker-gen](https://github.com/helderco/docker-gen). Be advised that for now, this works to a very limited extent [(everything has to be on the same node)](https://github.com/nginx-proxy/acme-companion/pull/231#issuecomment-330624331).
|
||||
The advantage the `label` methods have over the `environment variable` (and `volumes_from`) methods is enabling the use of the **acme-companion** in environments where containers names are dynamic, like in Swarm Mode or in Docker Cloud. Howhever if you intend to do so, as upstream **docker-gen** lacks the ability to identify containers from labels, you'll need both to either use the two containers setup or to replace nginx-proxy/docker-gen with a fork that has this ability like [herlderco/docker-gen](https://github.com/helderco/docker-gen). Be advised that for now, this works to a very limited extent [(everything has to be on the same node)](https://github.com/nginx-proxy/acme-companion/pull/231#issuecomment-330624331).
|
||||
|
||||
#### Examples with three containers setups:
|
||||
|
||||
|
@ -32,7 +32,7 @@ $ docker run --detach \
|
|||
$ docker run --detach \
|
||||
[...]
|
||||
--label com.github.jrcs.letsencrypt_nginx_proxy_companion.docker_gen \
|
||||
jwilder/docker-gen
|
||||
nginxproxy/docker-gen
|
||||
|
||||
$ docker run --detach \
|
||||
[...]
|
||||
|
@ -49,7 +49,7 @@ $ docker run --detach \
|
|||
$ docker run --detach \
|
||||
[...]
|
||||
--name another-unique-container-name \
|
||||
jwilder/docker-gen
|
||||
nginxproxy/docker-gen
|
||||
|
||||
$ docker run --detach \
|
||||
[...]
|
||||
|
@ -68,7 +68,7 @@ $ docker run --detach \
|
|||
$ docker run --detach \
|
||||
[...]
|
||||
--label com.github.jrcs.letsencrypt_nginx_proxy_companion.docker_gen \
|
||||
jwilder/docker-gen
|
||||
nginxproxy/docker-gen
|
||||
|
||||
$ docker run --detach \
|
||||
[...]
|
||||
|
@ -86,7 +86,7 @@ $ docker run --detach \
|
|||
$ docker run --detach \
|
||||
[...]
|
||||
--name another-unique-container-name \
|
||||
jwilder/docker-gen
|
||||
nginxproxy/docker-gen
|
||||
|
||||
$ docker run --detach \
|
||||
[...]
|
||||
|
|
Loading…
Reference in New Issue