Use Wireguard which has been merged into kernel (>= 5.6) about docker-wireguard HOT 7 CLOSED

Thanks for opening your first issue here! Be sure to follow the issue template!

from docker-wireguard.

It already works with built in kernel modules, but the module needs to be loaded and active. You may need to enable it on host first with modprobe

from docker-wireguard.

sudo modprobe wireguard did the trick, thanks so much @aptalca ! I'm going to make a PR to add this note to the README, I think it easily makes this images works on non-Debian systems.

from docker-wireguard.

Actually just saw the note about not making a PR for README updates. Here's what I was going to add:

If you're running a host with a more recent kernel, such as Fedora, the wireguard module may be built in. If this is the case, then you only need to make sure it's loaded. To load it, use `modprobe wireguard` on the host. The container should then detect that it's loaded and continue without issue.

from docker-wireguard.

it's already covered in the readme..

During container start, it will first check if the wireguard module is already installed and loaded. If not, ...

from docker-wireguard.

@drizuid I agree that it's already in there, I think that a quick note mentioning modprobe wireguard would be useful for people since on several kernels I've tested now it's not loaded by default, and this is a fairly uncommon command.

from docker-wireguard.

Maybe aptalca will agree and make a change, but I disagree. It has been common to load modules since the 90s when you need them. If you compile wireguard into the kernel itself rather than as a module, it will work without effort at all.

from docker-wireguard.