Errors running container
onestix opened this issue · comments
Hi @bubuntux, thanks for taking your time to start this project, it is much appreciated. I am hoping that this can solve some of my speed limitations that I have been having with the https://github.com/bubuntux/nordvpn repo.
I am aware that you have just recently started working on this, but wanted to share my first experience here:
I am running docker on a Synology DS918+ and have installed Wireguard using the https://github.com/runfalk/synology-wireguard repo on my NAS. Wireguard seems to be up and running fine and I did not specifically configure a wg0 config file. Now, when running the nordlynx container, I am getting a few errors:
Command:
sudo docker run -d --name=nordlynx --cap-add=NET_ADMIN -e PRIVATE_KEY=xxxxx --sysctl="net.ipv4.conf.all.src_valid_mark=1" -p 8001:8080 bbtux/nordlynx:latest
Log:
`[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-firewall: executing...
Firewall is up, everything has to go through the vpn
[cont-init.d] 00-firewall: exited 0.
[cont-init.d] 10-module: executing...
Uname info: Linux 6486bee3cce4 4.4.180+ #41890 SMP Fri Jun 25 02:42:35 CST 2021 x86_64 Linux
Wireguard module is active
[cont-init.d] 10-module: exited 0.
[cont-init.d] 20-inet: executing...
Enabling connection to secure interface and docker network
[cont-init.d] 20-inet: exited 0.
[cont-init.d] 20-inet6: executing...
No inet6 network
[cont-init.d] 20-inet6: exited 0.
[cont-init.d] 30-route: executing...
[cont-init.d] 30-route: exited 0.
[cont-init.d] 30-route6: executing...
[cont-init.d] 30-route6: exited 0.
[cont-init.d] 40-allowlist: executing...
[cont-init.d] 40-allowlist: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add 10.5.0.2/32 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] resolvconf -a wg0 -m 0 -x
[#] wg set wg0 fwmark 51820
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820
[#] ip -4 rule add not fwmark 51820 table 51820
[#] ip -4 rule add table main suppress_prefixlength 0
[#] iptables-restore -n
iptables-restore v1.8.7 (legacy): iptables-restore: unable to initialize table 'raw'
Error occurred at line: 1
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
[#] resolvconf -d wg0 -f
[#] ip -4 rule delete table 51820
[#] ip -4 rule delete table main suppress_prefixlength 0
[#] ip link delete dev wg0
`
Would you know what I am doing wrong here? Appreciate your help- thanks!
I moved it to nrdvpn/nordlynx instead of bbtux/nordlynx
but in any case... this container is a work in progress, tbh not sure what the problem is, seems host related since i'm being able to connect using regular amd64 host, i would recommend go back to a functional container for the moment, i'll keep working on this version but i just haven't found the time.
Hi @bubuntux, I managed to narrow down my issue here.
It seems that the Allowed IPs config of 0.0.0.0/0 is causing Wireguard to crash (due to an older kernel version on my Synology). I tried installing the Linuxserver Wireguard repo and adjusting it to 0.0.0.0/1. This worked well for me and the connection got initialised. Would it be possible for you to make the Allowed IPs value available as an env? The following comment describes my exact issue and solution: linuxserver#60 (comment)
Thanks for your help!
def can add it, i'll do soon
pull latest image and use env variable ALLOWED_IPS
Thanks @bubuntux - this worked well for me and I managed to get a successful handshake/connection. I am however having some trouble with the internet connection. The container is unable to resolve hosts. I have posted a message on the discussion board: #1 (reply in thread)