compose-transmission-wireguard VS docker-deluge-wireguard

transmission-wireguard - This is just a simple docker-compose config which combines transmission with a wireguard tunnel, and ensures that no transmission traffic goes outside the tunnel.

Yes, the config files are available in the directory and are set up as the instructions (https://github.com/SebDanielsson/compose-transmission-wireguard/blob/main/transmission.env). I do have a port named in transmission.env but again, I don't know if it's the right value. That's the whole crux of the original post.

https://github.com/haugene/docker-transmission-openvpn/ has a killswitch if you need it. There are also ones for wireguard: https://github.com/SebDanielsson/compose-transmission-wireguard.

I have been migrating my old bare-metal Ubuntu Setup to unRAID, and one of my big questions is on the previous machine, I used This Compose File to route Transmission into a Wireguard container to my self-hosted VPN in a different country. Now, the TransmissionVPN apps on the Community Apps store only has OpenVPN support, and little bits and pieces tell me Wireguard is supported, but I can't figure it out.

I use this on my Plex box and it works flawlessly. Transmission handles torrenting and it's passed over Wireguard with a killswitch but it's all containerized so it doesn't effect Plex or anything else on my server/network.

Ah but that one doesn't include the VPN. I've also seen them using Deluge+Wireguard.