binhex / arch-sabnzbdvpn

Docker build script for Arch Linux base with SABnzbd, Privoxy and OpenVPN
GNU General Public License v3.0
51 stars 9 forks source link

Very slow docker start #31

Open Tuumke opened 2 years ago

Tuumke commented 2 years ago

For some reason, this docker is super slow in starting up. It works fine, download speeds are fine as well. Unpacking can seem a bit slow maybe? But the startup of the docker is just..

Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2022-09-26 01:45:47.373355 [info] System information Linux 6de6286188a3 5.15.46-Unraid #1 SMP Fri Jun 10 11:08:41 PDT 2022 x86_64 GNU/Linux
2022-09-26 01:45:47.419925 [info] OS_ARCH defined as 'x86-64'
2022-09-26 01:45:47.451042 [info] PUID defined as '1000'
2022-09-26 01:45:59.230372 [info] PGID defined as '100'
2022-09-26 01:46:12.587982 [info] UMASK defined as '000'
2022-09-26 01:46:13.003205 [info] Permissions already set for '/config'
2022-09-26 01:46:13.481985 [info] Deleting files in /tmp (non recursive)...
2022-09-26 01:46:14.153743 [info] VPN_ENABLED defined as 'yes'
2022-09-26 01:46:14.186308 [info] VPN_CLIENT defined as 'wireguard'
2022-09-26 01:46:14.218447 [info] VPN_PROV defined as 'pia'
2022-09-26 01:46:24.425785 [info] VPN_CONFIG not defined (wireguard config doesnt file exists), defaulting to '/config/wireguard/wg0.conf'
2022-09-26 01:46:24.453929 [info] VPN_REMOTE_SERVER not defined (wireguard config doesnt file exists), defaulting to 'nl-amsterdam.privacy.network'
2022-09-26 01:46:25.618514 [info] VPN_REMOTE_PORT not defined (wireguard config file doesnt exists), identified port as '1337'
2022-09-26 01:46:25.651377 [info] VPN_DEVICE_TYPE defined as 'wg0'
2022-09-26 01:46:25.691588 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
2022-09-26 01:46:25.724779 [info] LAN_NETWORK defined as '192.168.90.0/24,10.253.0.0/24'
2022-09-26 01:46:25.759491 [info] NAME_SERVERS defined as '84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
2022-09-26 01:46:25.791589 [info] VPN_USER defined as 'xxxxxxxx'
2022-09-26 01:46:25.822275 [info] VPN_PASS defined as 'yyyyyyyy'
2022-09-26 01:46:25.856505 [info] STRICT_PORT_FORWARD defined as 'yes'
2022-09-26 01:46:25.888317 [info] ENABLE_PRIVOXY defined as 'no'
2022-09-26 01:46:25.922267 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2022-09-26 01:46:25.963960 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports

After that last line, it just seems to hang completely.

docker-compose:

  sabnzbd-vpn:
    <<: *common-keys-media # See EXTENSION FIELDS at the top
    image: binhex/arch-sabnzbdvpn
    container_name: sabnzbd
    privileged: true
    networks:
      t2_proxy:
        ipv4_address: ${T2_PROXY:-192.168.90}.24
    volumes:
      - $DOCKERDIR/sabnzbd/data:/data
      - $DOCKERDIR/sabnzbd/config:/config
      - /mnt/user/downloads:/downloads
      - /etc/localtime:/etc/localtime:ro
    environment:
      - PUID=$PUID
      - PGID=$PGID
      - VPN_ENABLED=yes
      - VPN_USER=xxxxxxxxx
      - VPN_PASS=yyyyyyyyy
      - VPN_PROV=pia
      - VPN_CLIENT=openvpn
      - STRICT_PORT_FORWARD=yes
      - ENABLE_PRIVOXY=no
      - LAN_NETWORK=192.168.90.0/24
      - NAME_SERVERS=84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1
      - sabnzbd_DAEMON_LOG_LEVEL=debug
      - sabnzbd_WEB_LOG_LEVEL=debug
      - DEBUG=true
      - UMASK=000

I'd expect more output then what i'm seeing now in the logs? But this is all i have in the docker logs -f sabnzbd command.

-edit- In the compose i had vpn_client set to wireguard, only changed to that after i was having these issues.

-edit2- I'm also running Deluge with VPN and setup Privoxy with VPN. Not sure if that matters but they both work fine.

-edit3- Ran with binhex/arch-sabnzbdvpn:3.5.3-1-03, seems to work pretty well.

-edit4- Spoke too soon i guess. Same behavior now.

-edit5- Still going with binhex/arch-sabnzbdvpn:3.5.3-1-03 since that at least gives me a VPN connection now

skjelmose commented 1 year ago

I have the exact same issue ... just hangs. Trying binhex/arch-sabnzbdvpn:3.5.3-1-03

skjelmose commented 1 year ago

I have the exact same issue ... just hangs. Trying binhex/arch-sabnzbdvpn:3.5.3-1-03

Worked! thanks