binhex / arch-qbittorrentvpn

Docker build script for Arch Linux base with qBittorrent, Privoxy and OpenVPN
GNU General Public License v3.0
445 stars 47 forks source link

qBitTorrent can't start because... I don't know #29

Closed UntouchedWagons closed 4 years ago

UntouchedWagons commented 4 years ago

I'm trying to incorporate arch-qbittorrentvpn into a docker stack along with some other services and qbittorrent is being troublesome

Container log: https://paste.dimdev.org/igamejalub.pl Relevant info from docker-compose.yaml

qbittorrent:
  image: binhex/arch-qbittorrentvpn
  container_name: qbittorrent
  restart: unless-stopped
  privileged: true
  volumes:
    - /etc/localtime:/etc/localtime
    - /mnt/data:/mnt/data
    - ./appdata/qbittorrent:/config
  ports:
    - 8118:8118
  cap_add:
    - NET_ADMIN
  environment:
    - VPN_ENABLED=yes
    - VPN_USER=obviouslynotmyrealusername
    - VPN_PASS=obviouslynotmyrealpassword
    - VPN_PROV=airvpn
    - ENABLE_PRIVOXY=yes
    - LAN_NETWORK=192.168.0.0/24
    - NAME_SERVERS=208.67.222.222
    - WEBUI_PORT=8080
    - UMASK=500
    - PUID=500
    - PGID=500

For some reason, ./appdata/qbittorrent/qBittorrent has a folder mask of 0377 which probably has a role in this issue.

UntouchedWagons commented 4 years ago

I just realized that UMASK is supposed to be file permissions. I changed it to 000 as the original example and qbittorrent can start. But I can't connect to its web UI even if I map port 8080 to the host.

binhex commented 4 years ago

you will need to either chmod all your files/folder in /config or delete everything in /config and restart the container, as the stuff up with the umask will still be present with any files created.

UntouchedWagons commented 4 years ago

I stopped the container, ran sudo chown -R media:media qbittorrent/ and changed PUID and PGID to 500 and now it can start. I don't know why it couldn't start when I tried that earlier. Oh well at least it works. Thanks