Wireguard container wg0 - Unknown device type - Protocol not supported

I may be wrong, but I believe we found that the issue was with the 5.3 kernel… don’t quote me though, i can’t find the source right now.

So is there a workaround that I can use to get this working?

did you try upgrading (or downgrading) the kernel by any chance to get off the 5.3 train?

This is my config, you need to download and compile wireguard-dkms in host to be ok`

    image: linuxserver/wireguard:latest
    container_name: vpn
      - NET_ADMIN
      - SYS_MODULE
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - SERVERURL=vpn.domain.com
      - SERVERPORT=53753
      - PEERS=5
      - PEERDNS=
      - homelan
      - ${DOCKER_CONFIG}/wireguard/config:/config
      - /lib/modules:/lib/modules
      - 51820:51820/udp
      - net.ipv4.conf.all.src_valid_mark=1
      - net.ipv4.ip_forward=1
    restart: unless-stopped


We have a test build here that should prevent most kernel compile issues: lspipepr/wireguard:v1.0.20200513-pkg-9fe5b6c6-pr-39 It’s multi-arch

I don’t appear to be running the 5.3 kernel:

uname -a
Linux raspberrypi 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l GNU/Linux

just try it…

SAME issue?!?! :stuck_out_tongue: obviously not though right? just try what aptalca told you and it will likely fix your issue (which is NOT the same)

Took a while for me to update, but yes:
Update to kernel 5.4 fixed my issue.

thanks for letting us know. That said, while we know there was an issue with 5.3 kernels, the lsiodev link aptalca provided can/should resolve the issue without a kernel upgrade from now on.

glad you got sorted though!

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.