Different behavior in datasets with identical ACLs

Update - Jellyfin is working, but i need help with the other one.

Jellyfin likes to mount the media folder with SMB, so i can just have it log in as the same the user i log in as with SMB, which is the owner of the dataset. Jellyfin can read and play the stuff in there, and if i need to move files around or whatever, i can do that under the same user with SMB in a file browser.

the other problem dataset is a Downloads dataset used by qbittorrent that i needed help with yesterday in this thread. i have qbittorrent running as a custom docker compose through dockge as its own user. it mounts this dataset directly instead of with SMB. i need qbittorrent to be able to download to and seed from this dataset, and i also need to be able to go in there myself in a file browser to access the files it downloads. i’ve tried a bunch of different permissions permutations, but i can’t find one that works.

  • when i posted this thread, the qbittorrent user owned the dataset, and my user account had read/write/execute access in the ACL. however, i actually only had read access when i opened it up in a file browser - just like i had with the Media dataset in the OP.
  • if i make my user the owner, and give qbittorrent read/write/execute, then i can access existing files in the folder just fine. qbittorrent can see the existing files in /downloads itself, but can’t see any in /downloads/some_folder. it’s also unclear to me if it can actually seed the files it sees in /downloads. it can download new files, but when it does it owns them, so i can’t access them in a file browser.

it seems like i have two options.

  1. change the docker compose for qbittorrent so it runs as my user, instead of its own (preferably without having my password just there in cleartext in the compose).

  2. keep the users separate, but make it so qbittorrent and i have full permissions on files the other owns in this dataset. maybe that’s something i could do with User groups? i don’t know.