diff options
| author | Malfurious <m@lfurio.us> | 2023-08-12 19:15:54 -0400 |
|---|---|---|
| committer | Malfurious <m@lfurio.us> | 2023-08-12 19:15:54 -0400 |
| commit | 43a3d5cd4d816ca45fc0d725e161ed2a4bf066cf (patch) | |
| tree | a55489b7dbb0f3315bb6202bfe0152baa20141ee /docker-compose-acme.yml | |
| parent | 8c11e387364c4235935134bc65d7ecf279d055ff (diff) | |
| download | proxy-docker-43a3d5cd4d816ca45fc0d725e161ed2a4bf066cf.tar.gz proxy-docker-43a3d5cd4d816ca45fc0d725e161ed2a4bf066cf.zip | |
>They are not needed anyway.
turned out to be wrong
I had previously removed definitions for the container's
`container_name` parameters to troubleshoot an issue, but I had
misunderstood the cause of the problem. In fact, even though the use of
the NGINX_PROXY_CONTAINER variable on the acme service didn't appear in
any documentation I read, it _was_ serving a purpose in helping the two
containers communicate.
I still prefer to not use the container_name parameter, so instead,
apply the correct label to the main nginx-proxy container in this
configuration. This actually appears to be the first method used by
acme-companion to locate the container.
Signed-off-by: Malfurious <m@lfurio.us>
Diffstat (limited to 'docker-compose-acme.yml')
| -rw-r--r-- | docker-compose-acme.yml | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docker-compose-acme.yml b/docker-compose-acme.yml index 51ce003..eafaa38 100644 --- a/docker-compose-acme.yml +++ b/docker-compose-acme.yml @@ -28,6 +28,8 @@ services: ports: - "80:80" - "443:443" + labels: + - "com.github.nginx-proxy.nginx" # https://github.com/nginx-proxy/acme-companion acme-companion: |