Closed UntouchedWagons closed 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.
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.
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
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
For some reason, ./appdata/qbittorrent/qBittorrent has a folder mask of 0377 which probably has a role in this issue.