Implement Wireguard support

[haugene]

Breaking change

No

Proposed change

Adding support for Wireguard through a new image

Type of change

• Bugfix (non-breaking change which fixes an issue)
• New feature (which adds functionality to this container)
• Breaking change (fix/feature causing existing functionality to break)

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue: relates to #
• Link to documentation updated (if done separately): https://...

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[darmach]

Was this abandoned? I'd love to see this working!

[robbbbbie]

Was this abandoned? I'd love to see this working!

idk if it's abandoned but it is working. I just installed the transmission-wireguard image from #2608 yesterday and it's fantastic. example docker-compose file can be found here. only quirk when installing was that you need to rename your vpn .conf file to my_wg.conf.

also it's not as fully featured as the openvpn version. would love to have it support the ability to change the web ui. otherwise, the wireguard one is getting the job done and is multiple times faster than the openvpn one using the same vpn server.

[darmach]

Looks slightly dated. Did you try out this by any chance @robbbbbie ?: https://github.com/sebdanielsson/compose-transmission-wireguard/blob/main/compose.yaml