Cover8099

Hmm, well you linked it and it says it installs it clear as day. So I am at a loss. Sadly I have no experience with containers that could pose an explanation. I used a raspberry pi 4 running Ubuntu, but I can't imagine that affects the container installing a particular package

I found the cause of this problem. The ldns package was not installed on the container. This caused the /root/tools.sh script (which uses the drill command for DNS resolution) to fail quietly (command not found). Installing the package also instantly made it resolve again, which is nice. I will write a git issue to learn more, cause this is probably not expected behavior.

Hello, I've been using your arch-delugevpn container with no issues. Decided I didn't require deluge anymore so I went with arch-privoxyvpn. Getting weird behavior, the proxy works (connection to Wireguard and DNS), but the container claims a DNS Failure, which causes the wireguard interface to restart. Then It attempts to get DNS again until failure and the cycle continues. In the container I can resolve dns queries without issue. Did not find a similar problem in the thread, if I missed it, please let me know. supervisord.log