Routing Error

[unintended-consequences]

I am not good at container networking, but my docker logs shows Openvpn is spitting out:

Fri Jan 21 16:31:43 2022 /sbin/ip route add 109.123.122.214/32 via 172.23.0.1
Fri Jan 21 16:31:43 2022 /sbin/ip route del 0.0.0.0/0
Fri Jan 21 16:31:43 2022 /sbin/ip route add 0.0.0.0/0 via 10.10.8.9
Fri Jan 21 16:31:43 2022 /sbin/ip route add 10.10.8.1/32 via 10.10.8.9
RTNETLINK answers: File exists
Fri Jan 21 16:31:43 2022 ERROR: Linux route add command failed: external program exited with error status: 2

Is it potentially conflicting with my 10.162.0.0/16 home network?

I have recreated this error in a brand new clean docker-compose container:

version: "3.7"

services:

  transvpn:
    image: "haugene/transmission-openvpn"
    container_name: "transvpn"
    cap_add:
      - NET_ADMIN
    environment:
      - OPENVPN_PROVIDER=SLICKVPN
      - OPENVPN_CONFIG=United-Kingdom-London
      - [email protected]
      - OPENVPN_PASSWORD=xxx
      - LOCAL_NETWORK=10.162.110.0/24
    logging:
      driver: json-file
      options:
        max-size: 10m
    volumes:
      - $DOCKDIR/08-transvpn/data:/data
    ports:
      - 39091:9091
    labels:
      - flame.type=app
      - flame.name=Transmission
      - flame.url=http://docker:39091
      - flame.icon=cloud-download
    restart: unless-stopped

[pkishino]

A few questions,
Why no config mount?
What platform? If synology, please search here and issues.. it’s always causing problems..

[unintended-consequences]

No config mount -> just followed the sample docker-compose in the readme here: https://github.com/haugene/docker-transmission-openvpn/blob/master/README.md which didn't contain a config mount.

I have mounted a volume to /config now but error remains.

Platform -> Ubuntu VM host on Proxmox

[pkishino]

Can you check that privilege use is enabled? This causes problems on synology usually.
If that fixes it then that tells us something.
Looks like some permission..
You could try removing LOCAL_NETWORK or set it to 127.0.0.1 and see if container starts properly in the logs.. that would be useful info as well

[pkishino]

could this be related? #2168

[unintended-consequences]

ip r inside a bash shell in the container outputs:

10.10.8.1 dev tun0 scope link
10.10.8.9 dev tun0 proto kernel scope link src 10.10.8.10
10.162.110.0/24 via 172.19.0.1 dev eth0
109.123.122.214 via 172.19.0.1 dev eth0
172.19.0.0/16 dev eth0 proto kernel scope link src 172.19.0.2 

[edgd1er]

setting DROP_DEFAULT_ROUTE to true might help if there is a conflict with your local network range.