Sock proxy fails

[iargue]

Sat May  5 05:28:21 2018 Incoming Data Channel: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat May  5 05:28:21 2018 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:02
Sat May  5 05:28:21 2018 TUN/TAP device tun0 opened
Sat May  5 05:28:21 2018 TUN/TAP TX queue length set to 100
Sat May  5 05:28:21 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Sat May  5 05:28:21 2018 /sbin/ip link set dev tun0 up mtu 1500
Sat May  5 05:28:21 2018 /sbin/ip addr add dev tun0 10.4.99.65/16 broadcast 10.4.255.255
Sat May  5 05:28:21 2018 /etc/openvpn/up.sh tun0 1500 1558 10.4.99.65 255.255.0.0 init
May  5 05:28:22 (1525498102.909995) sockd[32]: error: /etc/sockd.conf: problem on line 2 near token "tun0": could not resolve hostname "tun0": Try again.
May  5 05:28:22 (1525498102.910379) sockd[32]: alert: mother[1/1]: shutting down
Starting dante
Sat May  5 05:28:26 2018 /sbin/ip route add 173.44.55.154/32 via 172.17.0.1
Sat May  5 05:28:26 2018 /sbin/ip route add 0.0.0.0/1 via 10.4.0.1
Sat May  5 05:28:26 2018 /sbin/ip route add 128.0.0.0/1 via 10.4.0.1
Sat May  5 05:28:26 2018 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Sat May  5 05:28:26 2018 Initialization Sequence Completed

Not sure why it's saying that it can't resolve tu0, when tun0 is listed as being up right before. Launching it via docker run --cap-add=NET_ADMIN -p 127.0.0.1:1080:1080 -v /airvpn:/airvpn oblique/airvpn