wg-access-server VS docker-wireguard-pia

I tried them all. I settled on wg-access-server.

Yes, at my startup we run https://github.com/Place1/wg-access-server inside our kubernetes clusters to give engineers access to local pods vs the k8s DNS (.svc.cluster.local). It works relatively well but we've had to make a couple modifications:

1. I had to deploy CoreDNS to our cluster and set up DNS query rewriting to redirect queries from .cluster.mystartup to *.svc.cluster.local because docker on OS X has issues resolving hostnames that end in .local

What is the difference from https://github.com/Place1/wg-access-server ?

Not sure why this is downvoted. I use a similar service that runs in docker just fine. https://github.com/Place1/wg-access-server

https://github.com/thrnz/docker-wireguard-pia works great for me

I'm in need of help & guidance here. I have a DS 1821+ running the latest DSM 7.1 packages. I've installed Docker and I'm running a few *arr's with no problem using using the information here (https://trash-guides.info/Hardlinks/How-to-setup-for/Synology/). I also have qBitTorrent working, but I'd like to have that traffic routed through a VPN. I installed this Docker image (https://github.com/thrnz/docker-wireguard-pia), but now I'm lost.

The stack (found here, and the extra variables here):

I have set up a new QNAP NAS and have a wireguard docker container that I've ported over to it. The container worked on a completely different system, but on the new QNAP NAS it won't work due to an issue with wg-quick and certain functions not being available on the QNAP kernal. The container in question uses the thrnz/docker-wireguard-pia image.

2) Also underrated because it's the only docker image for a VPN provider that supports portforwarding & automatically updates the configured port in QBittorrent settings: https://github.com/thrnz/docker-wireguard-pia