Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Partial downloads restart on container restart #117

Open
taschmidt opened this issue Nov 23, 2021 · 1 comment
Open

Partial downloads restart on container restart #117

taschmidt opened this issue Nov 23, 2021 · 1 comment

Comments

@taschmidt
Copy link

taschmidt commented Nov 23, 2021

First off, I've only been using this for a few days but I love it and want to thank you for your great work! The only issue I'm having is if a torrent is not complete when I shut down the container, it'll restart from 0% when starting back up. Any ideas why that would be?

Here is the docker compose file I'm using:

version: '3.6'

services:
  qbittorrent:
    image: binhex/arch-qbittorrentvpn
    container_name: qbittorrent
    restart: unless-stopped
    privileged: true
    ports:
      - 6881:6881
      - 6881:6881/udp
      - 8080:8080
      - 8118:8118
    volumes:
      - /d/torrents/downloads:/downloads
      - /d/torrents/config:/config
    cap_add:
      - NET_ADMIN
    environment:
      - VPN_ENABLED=yes
      - VPN_USER=<redacted>
      - VPN_PASS=<redacted>
      - VPN_PROV=pia
      - VPN_CLIENT=openvpn
      - STRICT_PORT_FORWARDING=yes
      - ENABLE_PRIVOXY=no
      - LAN_NETWORK=192.168.1.0/24
      - NAME_SERVERS=1.1.1.1,8.8.8.8
      - DEBUG=false
      - WEBUI_PORT=8080
      - UMASK=000
      - PUID=1000
      - PGID=1000

I'm running on Windows 11 with Docker Desktop 4.2.0 (70708).

@taschmidt
Copy link
Author

Quick update here. I was playing around with this and it seems like pausing a torrent before stopping the docker container will at least let qBT not start all the way from 0%. The obvious downside there is that torrent will be paused when qBT starts back up.

An interesting observation with this scenario, if I pause a torrent at, say, 5%, shut down the container, start it back up, resume the torrent, let it go to, say, 10%, stop the container WITHOUT pausing, start it back up.... the torrent will be back at 5% (i.e. the last place it was paused at. Does this make sense to anyone??

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant