- Minor
Hello,
I've been struggling with my other issue below, but maybe found a specific bug/fix for it. Therefor this new issue because it might not even fix the other one.
It seems like line 166 in rc.d/rc.docker is not entirely correct.
"[[ -n $NETWORK ]] && nsenter -n -t $PID ip -4 route add $NETWORK via $THISIP dev br0 2>/dev/null"
translates to
nsenter -n -t 9439 ip -4 route add 10.253.0.0 via 192.168.0.231 dev br0
If I understand it correctly, it attaches to the container process and adds a static route for wireguard. In my case 10.253.0.0/24 to 192.168.0.231. But it uses the br0 interface. This interface is not available within the docker container. The available interface is eth0. Therefor the command failes and the static route does not get created. The only thing I do not know is why this only happens on unraid/docker startup The static route will be added upon container restart. I believe the scripts doing both actions (initial startup / container restart) are not the same and that might explain it.