Lucas Lorentz

Fixed on version v2.3.3 Can you please try it and reopen the issue if you still face issues. Now after losing connection to docker events, it will properly close everything...

It seems that after a daemon restart the previously mounted docker.sock file is not functional anymore. For how long did you wait? Maybe docker API takes some time to become...

Or maybe this, so it will not have any sensitive information: ``` docker run -d -v /var/run/docker.sock:/var/run/docker.sock docker sh -c "while true; do docker version -f '{{json .Server.Platform.Name}}'; sleep 1;...

@danog Docker-compose prefixes the network names they create with your folder name. Probabbly your CADDY_INGRESS_NETWORKS config is incorrect because of that. You can force it to use the network name...

I think this is doable, and we had requests before to support json configuration. Maybe we can use json patch syntax.

CADDY_CONTROLLER_NETWORK only needs to be defined when executing separate "controller" and "server". The "controller" part connects to docker API and it could use it to find the network IP ranges...

It doesn't need to be exactly the same. It uses the CIDR to know on which interface caddy should bind to listen for controller configs: https://github.com/lucaslorentz/caddy-docker-proxy/blob/4893c4dbcfbdfefca0a6aa6510d79a42536e6c8a/plugin/cmd.go#L112 You need to make...

I will try later to set it to "tcp/0.0.0.0:2019" That might set it up to listen on all interfaces.

@HeavenVolkoff Thanks for the great investigation so far. I just had a look at the code again. The container id retrieval is part of a logic to determine which networks...

@HeavenVolkoff Readme updated!