wireguard-go-docker VS wg-gen-web

I thought wireguard-go requires the kernel tun device. See for example this Docker image for wireguard-go which maps the tun device and requires elevated permissions - https://github.com/masipcat/wireguard-go-docker

I was just curious if it's just me. It seems theres a few posts on various places on the internet on this and the questions are not answered on any of them (EG: https://github.com/masipcat/wireguard-go-docker/issues/19)

For client devices (like phones, laptops, workstations) i use wg-gen-web

If he goes funky there's always this: https://github.com/vx3r/wg-gen-web

I ended up working with wg-gen-web (https://github.com/vx3r/wg-gen-web). It’s pretty slick looking, easy to use, and after some struggles I managed to get authentication working. I also tweaked the docker image to change a few things to my liking (page title, etc). I still feel like this is the missing piece in WireGuard. I know it’s still new, but with this GUI, I have a pretty damn good solution for the few users I have that need it.

You would have to do some more Setup around it but wg-gen-web can do this

Not sure about running wireguard itself in a container but i've been running this GUI and the github page also provide some systemd hooks so that when the config changes, wireguard is restarted on the host.

There are scripts that generate the configs for you but also web services you can host yourself which also have a nice ui.

Your VPN (Wiregiard) is independent of that - it will allow you to access the Rpi itself from outside (as if you were in your LAN). I recommend https://github.com/vx3r/wg-gen-web to manage your WG configuration.