Fix regression in the full acme-companion configurationHEADmaster

>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>

0 files changed, 0 insertions, 0 deletions