-
-
Notifications
You must be signed in to change notification settings - Fork 208
Description
I use this in docker alongside a VPN (also in docker). sometimes the VPN connection dies and needs to be restarted. Docker's health checks along with the autoheal image can fix the VPN automatically.
But I've noticed that even after restarting the vpn, the proxy often remains broken and I'll see log messages like 2025/03/14 13:56:17 [ERR] socks: Failed to handle request: Failed to resolve destination '0': lookup 0: no such host and 2025/03/14 13:56:32 [ERR] socks: Failed to handle request: readfrom tcp 10.22.33.44:38908->111.222.333.444:443: splice: connection reset by peer until I restart the proxy container.
docker-compose doesn't support complicated restart dependencies and have decided that containers should quit if they're not working so that docker can restart them. So an option for "quit on errors" would certainly be helpful.