docker-autoheal VS gluetun

autoheal

Have you tried autoheal? It's a Test Driven Design-based "auto"-gpt. It iterates on your code until the tests you've created (or created via chatGPT) are passing. I have had mixed results, but I think having tests serves as a good north star for an agent to work toward.

Hello guys, I often have this issue where a container B uses the network of a container A and container A fails at some point. Also I have many dumb containers that will just fail on their own without being restarted. I tried the nice willfarrell's autoheal but it does not support dependencies. I did not want to migrate my setup to some k3s or something that would be way overkill for what I want.

I use autoheal and have the healthcheck below in my docker compose. I also have uptime-kuma monitoring the web page availability for alerting and Tautulli monitoring remote access availability.

As a workaround for this you could use autoheal to automatically restart the kuma container when it becomes unhealthy.

I useautoheal and i try to have a useful healthcheck on all my containers. It is only lacking any kind of notification if a container is unhealthy and is being restarded.

I've figured a workaround by adding a healthcheck to the docker-compose and running an autoheal container, but I just can't quite figure out why I need it in the first place.

Make sure to implement health hecks, so containers restart automatically when your vpn connection drops. Docker doesn't restart unhealthy containers automatically, but you van use autoheal for that. Also use the health status in the depends_on to make sure the containers start in the correct order (start the *arr containers after the vpn is running for example).

healthcheck: # https://github.com/qdm12/gluetun/issues/641#issuecomment-933856220 test: "curl -sf https://example.com || exit 1" interval: 1m timeout: 10s retries: 2

I have containers a,b,c. Container C is running Gluetun (https://github.com/qdm12/gluetun) which is a VPN container.

The last couple of years I have been donating to Gluetun.

One option I could find is Gluetun, which looks very popular and actively maintained. In this case we have one single point of contact with VPN provider. The other containers should be run with network_mode: service:gluetun. If I understand correctly, those container will use VPN for every network operation, even for inter-container communication. Would they be visible for the containers not attached to gluetun (e.g. the SWAG reverse proxy)?

Try setting it up. https://github.com/qdm12/gluetun See if it works for your needs.

After some digging around, I found this project, which I think should get a lot more light on itself. It allows to setup port-forwarding on linux very easily, together with a lot of other things !

I setup Gluetun with qbittorrent in docker. Gluetun connects to the nord via manual login and I get to choose the specific servers I want it to you in its environment variables.

Hi guys, I have a dumb question: according to their github page, one of the features is the killswitch. It is not clear to me whether this would shutdown other containers (connected to it) when vpn drops, or only when the whole internet connection goes down

# See https://github.com/qdm12/gluetun/wiki