wireguard-go-docker VS nordvpn

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)

version: "3.8" services: nordlynx: image: ghcr.io/bubuntux/nordlynx cap_add: - NET_ADMIN # Required environment: # Review https://github.com/bubuntux/nordvpn#environment-variables - PRIVATE_KEY=mykey # Required - CONNECT=United_States - NET_LOCAL=10.20.30.40/24 # So it can be accessed within the local network - ALLOWED_IPS=10.20.30.40/24 ports: - "6881:6881" #qbittorent - "6881:6881/udp" #qbittorrent - "8080:8080" #qbittorrent - "7878:7878" #radarr - "8989:8989" #sonarr - "9696:9696" #prowlarr - "8097:8096" #jellyfin - "5055:5055" #jellyseer sysctls: - net.ipv6.conf.all.disable_ipv6=1 # Recomended if using ipv4 only qbittorrent: image: linuxserver/qbittorrent container_name: qbittorrent network_mode: service:nordlynx environment: volumes: - /path/to/qbittorrent/config:/config - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped radarr: image: linuxserver/radarr container_name: radarr network_mode: service:nordlynx environment: volumes: - /path/to/radarr/config:/config - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped sonarr: image: linuxserver/sonarr container_name: sonarr network_mode: service:nordlynx environment: volumes: - /path/to/sonarr/config:/config - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped prowlarr: image: linuxserver/prowlarr container_name: prowlarr network_mode: service:nordlynx environment: volumes: - /path/to/prowlarr/config:/config depends_on: - nordlynx restart: unless-stopped jellyfin: image: linuxserver/jellyfin container_name: jellyfin network_mode: service:nordlynx environment: - JELLYFIN_PublishedServerUrl=http://10.20.30.184:8097/ volumes: - /path/to/jellyfin/config:/config - /path/to/jellyfin/cache:/cache - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped jellyseer: image: fallenbagel/jellyseerr:latest container_name: jellyseer network_mode: service:nordlynx environment: volumes: - /path/to/jellyseer/config:/app/config depends_on: - nordlynx restart: unless-stopped

All the infos you need are on the github page > https://github.com/bubuntux/nordvpn

Issues · bubuntux/nordvpn (github.com)

On https://github.com/bubuntux/nordvpn it mentions that token login is also supported (Nord v3.15.0+). I've used the token login and it works well for me.

There has been an issue reported on github: https://github.com/bubuntux/nordvpn/issues/367

Two of the popular containers are https://github.com/qdm12/gluetun and https://github.com/bubuntux/nordvpn but it's not clear if either of them can use meshnet.

A ubuntu/debian vm with nordvpn official client, use iptables to forward this connection to the vm IP. I've seen a similar approach using docker here https://github.com/bubuntux/nordvpn but this only shares connection to other dockers ct's in the same setup