search

soxfor / qbittorrent-natmap

The objective of this container is to run a script that requests a port forward (via NAT-PMP) from the VPN provider and upon success changes the listening port of the qBittorrent client when running in Docker
133 stars 17 forks source link

healthcheck makes it fail on wireguard #15

Open davidzx opened 1 year ago

davidzx commented 1 year ago

hey i got it working with gluetun, but the Linuxserver[dot]io wireguard container won't work. the natmap container just hangs on the health check. would be nice to be able to turn off the health check, so it might work with other wireguard containers.

heim3x commented 11 months ago

You can add this healthcheck to the Wireguard container as a workaround.

    healthcheck:
      test: ["CMD-SHELL", "ip link show wg0 || exit 1"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 15s
defconxt commented 7 months ago

@davidzx is this what you are referencing? I am having the same issue I think.

I see in my gluetun that I am successfully connected to my VPN, also qbittorrent is successfully connected on 8080 and I am able to reach the interface, but then I exec into the qbittorrent-natmap container and its spamming this below, even though the gluetun container is "healthy". I tried manually running the script there as well and still no luck. Not sure how to fix this.

defcon@plex:~$ sudo docker exec -it bda45870e035 /bin/bash
root@15f8682357a7:/# ls
bin  boot  dev  etc  home  lib  lib32  lib64  libx32  media  mnt  opt  proc  root  run  sbin  srv  start.sh  sys  tmp  usr  var

root@15f8682357a7:/# ./start.sh

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
2023-11-21 02:30:45 | Waiting for gluetun healthy state..
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
2023-11-21 02:30:48 | Waiting for gluetun healthy state..