Quentin McGaw

Yes that's a good idea, thanks! In the meantime, you could change the healthcheck settings of your container (see [docker run healthcheck docs](https://docs.docker.com/engine/reference/run/#healthcheck)) so it would only be as unhealthy...

> time to go healthy after starting and deunhealth restarts it over and over It most likely goes unhealthy then (although for a split millisecond and then gets restarted). Deunhealth...

Can you share your deunhealth full logs and docker-compose.yml please?

That's really strange. So the container can no longer be found with its container ID?! I'll do some more testing. Meanwhile I'm almost done on a cascaded restart feature which...

Ah got it. It's because the container ID it was relying on (gluetun) disappeared. Ugh, that's also going to be problematic for my cascaded restart feature... I think the (connected)...

Ok so after some research... There is no way to know what the 'vpn' container was since we just have its ID and it no longer exists (the name is...

So... this previous suggestion, let's call it `A`, won't work if Deunhealth starts and a VPN container has already been shutdown/restarted and existing containers are disconnected, before deunhealth started. The...

I'm working on it right now! Hopefully we will have something today :wink: EDIT (2021-12-06): still working on it, it's a bit more convoluted than I expected code-spaghetti wise, but...

Note if the 'network container' (aka the vpn) goes down and doesn't restart, there is no way to restart properly the connected containers since the label won't be anywhere unfortunately....

Hello all, good news, I'm working again on this. Sorry for the immense delay I took to get back working on this. I have some 'new uncommited' code (from like...