- #SONARR KICKASS NOT WORKING INSTALL#
- #SONARR KICKASS NOT WORKING UPDATE#
- #SONARR KICKASS NOT WORKING FULL#
- #SONARR KICKASS NOT WORKING SERIES#
- #SONARR KICKASS NOT WORKING DOWNLOAD#
#SONARR KICKASS NOT WORKING INSTALL#
To install and use these Docker images, you'll need to keep the above in mind while following their documentation.
#SONARR KICKASS NOT WORKING DOWNLOAD#
Keep in mind that Sonarr will need read and write to the download folders as well as the final folders.įor a more detailed explanation of these issues, see The Best Docker Setup and Docker Guide wiki article. The recommendation is to use a common group for all related containers so that each container can use the shared group permissions to read and write files on the mounted volumes. The default user, group and umask, you should decide this before setting up all of your containers. Most images have environment variables that can be used to override Permissions and ownership of files is one of the most common problems for Sonarr users, both inside and outside Docker. If this advice is not followed, you may have to configure a Remote Path Mapping in the Sonarr web UI (Settings › Download Clients).
#SONARR KICKASS NOT WORKING SERIES#
Your Series would be in /data/tv, torrents in /data/downloads/torrents and/or usenet downloads in /data/downloads/usenet. The best solution is to use a single, common volume inside the containers, Some also recommend paths for the download client container that are different from the Sonarr container, like /torrents. This causes slow moves and doesn't allow hard links because they are considered two different file systems inside Most Docker images suggest paths like /tv and /downloads. Both problems can be solved with well planned, consistent paths. The second is a performance issue and causes problems for seeding torrents. The first is a problem because the download client will report a download's path as /torrents/My.Show.S01E01/, but in the Sonarr container that might be at There are two common problems with Docker volumes: Paths that differ between the Sonarr and download client container and paths that prevent fast moves and hard links.
Of course, it is always advisable to make a backup first. Sonarr v3 will convert the given directory on startup if a Sonarr v2 database is found. You’ve also shared 0 logs, what user/group sonarr is running as, or ls - lha of anything as well.Most docker containers use /config volume to mount the data directory and supply that path to Sonarr as parameter. every single one of those users either realizes the issue is theirs and fixes it…later admitting “oh yeah I did change X” or refuses to accept reality, wrongly blames the app, and storms off in a huff never to be heard from again nor ever fixing their problem.
#SONARR KICKASS NOT WORKING UPDATE#
So far all you’ve done is claimed you changed nothing and somehow Sonarr magically had an update that makes it unable to see folders it has permissions to…and yet you’re the only person this is occurring for…so it’s clearly an issue with your environment and your permissions…just like it is every single time users claim their setup and permissions are perfect and Sonarr has a bug/is lying/etc. The issue is plain and simple 1) you cannot add a series without assigning it a root folder and 2) you cannot add a root folder without the user Sonarr is running as having Read/Write access to the folder. It’s not a Sonarr issue as Sonarr has no control over what it can or cannot access.
Now is there a way to get Sonarr to go ahead and add a show with out the root folder being selected? I should never have to open a terminal to fix permissions.
#SONARR KICKASS NOT WORKING FULL#
New as for how I deal with permissions is by installing kde-servicemenus-rootactions, rightclicking in the folder I want full permission in, selecting ownership to active user from the root actions menu.
Sonarr witrh all it’s features for automating everything is great, don’t get me wrong there but for some of us we do not need all the feature because of the way we handle our files. Some of us just use Sonarr to grab and download and nothing else, so in this case all sonarr is doing is grabbing the file and passing it to the download client and nothing more. Secondly having or not having a root folder should have NOTHING to do with the ability to add new shows to Sonarr. The fact that there is a issue adding a root folder back is a Sonarr issue. No matter how the root folder disappeared since Sonarr already had permission to access that folder there should be no issue in adding it back and or changing it, especially since the permissions for the partition / folder it was pointed to have not changed.
0 kommentar(er)
