arch-delugevpn VS docker-autoheal

Basically, I would like that few of my containers to use a proxy whenever they need to access the external world (e.g. Sonarr and its friends). At the moment, for Deluge I am using binhex docker image, an all in one solution for torrent, vpn and so on. Just to add an extra security layer, I would like to obfuscate from my ISP all the calls that the *Arr friends are doing to the usual search engines.

Solution in the end was to just find a pre-created docker image that handled both I used https://github.com/binhex/arch-delugevpn but there seem to be qbittorrent equivalents out there.

Check it out, read the full page and have another go: https://github.com/binhex/arch-delugevpn

https://github.com/binhex/arch-qbittorrentvpn https://github.com/binhex/arch-delugevpn

Vpn killswitch Torrent clients: rutorrent deluge qbittorrent

Are you wanting to use your VPN for anything other than your torrent traffic? If not, an easier method might just be to grab an container that has VPN+torrent client in one. Like this: https://github.com/binhex/arch-delugevpn

Is arch-delugevpn still a popular route to go? Would like to use deluge or qbittorrent if possible.

DSM 7.1.1-42962 Update 3 was auto-installed on my DS220+ last night and today I can't access the web UI for binhex arch-delugevpn.

Seeing how the latest docker image arch-delugevpn doesn't work in DSM 7 (Kernel Too Old Message), what is the last known working version of Arch-Delugevpn that does work in DSM 7?

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