Qbittorrent container not able to write config changes

  • I've been using OMV for about 5 years. Finally made the leap to v7 from v5 (skipped 6 entirely). Everything is working as intended except one thing: my qbittorrent container, which is fully functional and playing nice with all my *arr containers, will not save any config changes within the webgui. Hitting save does nothing. Nothing comes up in the container logs either. So I thought I have a permission issue; after spending some time trying to fix permissions with no results I ended up nuking the appdata folder and pulling the container again. I get same result, with a completely fresh container. This container has the same UID/GID as my *arr instances. I have temporarily set up transmission while I figure this out. It seems like all my other containers have no permission problems using the appdata mount point I have. Transmission seems to have no problems at all saving config options in the webgui . Here is my docker compose:


  • What is the output of this command:


    Code
    ls -al /srv/WDC-Array/appdata/qbittorrent

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.


  • Code
    total 16
    drwxr-sr-x+  4 Cian users 4096 Jul  4 23:40 .
    drwxrwsr-x+ 26 root users 4096 Jul  5 00:18 ..
    drwxrwsr-x+  3 Cian users 4096 Jul  4 23:40 .cache
    drwxrwsr-x+  6 Cian users 4096 Jul  5 00:14 qBittorrent
  • There is a known bug that may be causing this in QBT v5.1.1. If you are running that version, see if v5.1.2 is out or downgrade to v5.1.0.


    See:


    https://github.com/qbittorrent/qBittorrent/issues/22909

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.


  • Cian00

    Added the Label resolved
  • Thank you very much! I'm amazed I didn't find that issue on github. Just span up a new qBitottorent container on v5.1.2 and it's working fine now. I was convinced the problem was my limited understanding of permissions.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!