You run Sonarr using linuxserver/sonarr, you’ve created a sonarr user with uid 123 and a shared group media with gid 321 which the sonarr user is a member of. Perhaps let one system pick the UID/GIDs, then re-use those on the other system, assuming they don't conflict. If you're using storage from another system via NFS or CIFS, it will make your life easier if that system also has matching users and group. If you ever peak in, you'll find that username is something like abc or nobody, but because it uses the UID/GID you pass in, on the outside it looks like the expected user. Many docker images also take a -e PUID=123 and -e PGID=321 that lets you change the UID/GID used inside to that of an account on the outside.
QBITTORRENT WITH SONARR SETUP SOFTWARE
If you're using existing folders and files, you'll need to fix their current ownership and permissions too, but going forward they'll be correct because you set each software up right. This will ensure that files and folders created by one can be read and written by the others. Many docker images accept a -e UMASK=002 environment variable and some software inside can be configured with a user, group and umask or folder/file permission (Sonarr/Radarr). For a deeper explanation, try the Arch Linux wiki articles about File permissions and attributes and Umask. You can restrict permissions even more by denying read from “other”, which would be a umask of 007 for a user per daemon or 077 for a single shared user. A sane alternative to this is a single shared user, which would use 775 and 664which is a umask of 022. Ideally, each software runs as its own user and they’re all part of a shared group with folder permissions set to 775 ( drwxrwxr-x) and files set to 664 ( -rw-rw-r-), which is a umask of 002. This is easy to say, but difficult to understand and explain. The idea is that each docker container is run as its own user, with a shared group and consistent volumes so every container sees the same path layout. The following article will not show specifics about the best Docker setup, but it describes an overview that one can use to make its own setup the best it can be.
![qbittorrent with sonarr setup qbittorrent with sonarr setup](https://charly3pins.dev/images/raspberry-media-player/installation.jpg)
And most of all, ignore most of the path suggestions from the Docker image documentation! Consistent paths between all containers which match on the inside and outside that appear as one file system for Sonarr, Radarr and Lidarr so hard links are possible and moves are atomic. TL DR: A shared user per daemon and a shared group with a umask of 022. I remind you that content piracy is illegal and a punishable offence under the laws of Mauritius.
![qbittorrent with sonarr setup qbittorrent with sonarr setup](https://i.ytimg.com/vi/Cth-bsLAa_M/sddefault.jpg)
I do not encourage content piracy in any way whatsoever. DISCLAIMER: This work is for research and education purpose only.