search

MarkusMcNugen / docker-qBittorrentvpn

Docker container which runs a headless qBittorrent client with WebUI and optional OpenVPN
https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/
GNU General Public License v3.0
166 stars 92 forks source link

Synology NAS - RTNETLINK error for WireGuard #158

Closed goooroooX closed 12 months ago

goooroooX commented 12 months ago

Hi! I'm trying to run this image on Synology DS220+ NAS as docker container. I've tried adding NET_ADMIN privileges, and also running in privileged mode.

The error always the same:

2023-07-13 13:31:23.792726 [INFO] Starting WireGuard...
Warning: `/config/wireguard/wg0.conf' is world accessible
[#] ip link add wg0 type wireguard
RTNETLINK answers: Operation not supported
Unable to access interface: Protocol not supported
[#] ip link delete dev wg0
Cannot find device "wg0"

Can you please suggest how to fix this?

goooroooX commented 12 months ago

WireGuard kernel modules should be installed first, in order to make this container work on Synology. Compiled packages can be downloaded here: https://www.blackvoid.club/wireguard-spk-for-your-synology-nas/

However, container is still shutting down after a while, saying "Network is possibly down". Also, there are many iptables errors while starting the container. Log file is attached.

synology-log.txt

Most errors are similar to those:

iptables v1.8.7 (nf_tables): unknown option "--sport"
iptables v1.8.7 (nf_tables): unknown option "--dport"
iptables v1.8.7 (nf_tables): unknown option "--icmp-type"
iptables v1.8.7 (nf_tables): Could not fetch rule set generation id: Invalid argument

Related issue: https://github.com/DyonR/docker-qbittorrentvpn/issues/25 Iptables issues can be fixed with setting LEGACY_IPTABLES env. variable to 1, but "Network is possibly down" and container automatic shutdown is still there.

goooroooX commented 12 months ago

Wrong repository, apologize. This issue should be here: https://github.com/DyonR/docker-qbittorrentvpn