Sonarr Unable to Import, Permissions Issue?

Hi I'm on OMV 6.4.4-1 (Shaitan) currently using a docker-compose file for several containers including sonarr. I am having issues setting up my folder permissions to get sonarr to successfully import. I wanted to double check my docker-compose to make sure I'm doing the right thing for the shared folders connected to it.

I ran id myusername to get my PUID and PGID.

In my Shared Folders/ACL page, My username has read/write access, the owner is myusername, group is users. Both have read/write/execute permissions. What else do I need to configure? This appears to be a shared folder permissions issue. Thank you

root@omv:/home/docker# id myusername
uid=1000(myusername) gid=100(users) groups=100(users),0(root),1(daemon),2(bin),4(adm),6(disk),7(lp),24(cdrom),29(audio),34(backup),37(operator),65534(nogroup),107(crontab),108(netdev),109(ssl-cert),113(ssh),114(_chrony),115(avahi),116(sambashare),999(openmediavault-config),998(openmediavault-engined),997(openmediavault-admin),996(openmediavault-webgui),995(openmediavault-notify),992(docker),117(qbittorrent-nox)

sonarr:
image: lscr.io/linuxserver/sonarr:latest
container_name: sonarr
environment:
- PUID=1000
- PUID=100
- TZ=America/Los_Angeles
volumes:
- ./sonarr:/config
- /srv/dev-disk-by-uuid-XXXXXXX-XXXX-XXXX-XXXX-a9393c087104:/14TB
- /srv/dev-disk-by-uuid-XXXXXXX-XXXX-XXXX-XXXX-90ccadc28761:/8TB
ports:
- 8989:8989
restart: unless-stopped

Quote from gderf

[…]

those drives are mounted so sonarr can see. these are my 2 shared drives connected via usb

Quote from BernH

Also don’t put your sonarr config in ./sonarr. It’s better map that to a finite application data directory on one of those shared drives such as

- /srv/dev-disk-by-uuid-XXXXXXX-XXXX-XXXX-XXXX-a9393c087104/appdata/sonarr:/config

Using that appdata directory as a root for all docker config files will make the app configurations and databases be persistent and survive docker pruning or OS re-installs.

Thank you. I have my docker-compose.yml stored in /home/docker/, so when you see ./sonarr the real address is /home/docker/sonarr. Which is on my SSD where OMV is installed, not the 2 shared drives

Is this still bad practice?

I still have a permissions issue and my configuration seems normal from what I see in Sonarr documentation. I believe it's shared folder permissions, is there a guide to just get 755 or 755 chmod done for the folders? The GUI has a learning cover for this page and command line for chmod isn't allowed it seems.

Quote from BernH

It's best to store all compose files and the config files in a directory that is not in a user's home directory. Home directories are owned by the user, so ownership of the files can cause issues. If they are not in a home directory, then they can be fully accessible to other users and you can deal with the permissions easier, and as I mentioned it will survive an os re-install.

Would I be okay if I move the docker folder to the same level of the home folder, and not nested within? So instead of /home/docker/docker-compose.yml it's /docker/docker-compose.yml

What about shared folders? Can you guide me to the best practice for this so my qbittorrent, sonarr, radarr, sonarr play nice with it (in terms of being able to write)? Currently it seems like I can read off it but not write to it.

Below is my Permissions that I see in OMV web UI. The blacked out part is my only user created. I wish I could just type in a chmod 3 digit number instead

Quote from BernH

Ok, so going back through your posts, firstly, I see an error in your sonarr compose file.

You have:

Code

environment:
- PUID=1000
- PUID=100

The second one should be: PGID=100 not a second PUID. PUID is User ID, PGID is Group ID.

Your Volumes in that same compose is:

Code

volumes:
- ./sonarr:/config
- /srv/dev-disk-by-uuid-XXXXXXX-XXXX-XXXX-XXXX-a9393c087104:/14TB
- /srv/dev-disk-by-uuid-XXXXXXX-XXXX-XXXX-XXXX-90ccadc28761:/8TB

OMV likes things to be in sub-directories of the root, not the root itself, so you should have something like this:

Code

volumes:
- ./sonarr:/config
- /srv/dev-disk-by-uuid-XXXXXXX-XXXX-XXXX-XXXX-a9393c087104/media:/14TB
- /srv/dev-disk-by-uuid-XXXXXXX-XXXX-XXXX-XXXX-90ccadc28761/media:/8TB

Then all your media should be in the media directories, or whatever you want to call them. The /14TB and /8TB would end up being the paths that sonarr sees inside the container

Your docker storage path should ideally be something like this:

/srv/dev-disk-by-uuid-XXXXXXX-XXXX-XXXX-XXXX-a9393c087104/appdata or whatever you want to call it.

And likewise your shared directory for the compose files should be something like:

/srv/dev-disk-by-uuid-XXXXXXX-XXXX-XXXX-XXXX-a9393c087104/compose-files or whatever you want to call it.

This will keep all the docker related files off of your OS drive so that an OS reinstall will not kill all your docker containers. If you had to re-install, all you would need to do is set the docker storage path again and the dockers would all start up and keep any data that was created by them previously.

Once you set those docker directories, you can stop docker, move all the existing docker directories into those directories and then start it up again and everything should come to life.

You would also need to fix the permissions screen shot you sent so that it is pointing to the sub-directory your shared media directory is called , not the drive root.

As a general rule too, I would recommend that you use the reset permissions plugin to remove those ACLs you made. ACLs can be powerful, but can create a lot of complexity between different user accounts and system accounts. Generally you don't need them for basic shared folders, just the regular shared folders permissions.

Display More

thank you so much! I've followed the instructions to start for the reset permissions plugin, then I went back to apply. My permissions look like this now. Importing works now in my radarr/sonarr apps now.