Our recommendation is to use a single volume for the data, as mentioned above. The default volumes are not optimal nor recommended. LinuxServer specifies a couple of optional default volumes such as /tv and /downloads. They also maintain images for most of the popular download clients as well. Linuxserver.io is one of the most prolific and popular Docker image maintainers. Read the instructions on how to install the image. Images are automatically updated multiple times per hour if upstream changes are found. Hotio doesn't specify any default volumes, besides /config. There are many ways to manage Docker images and containers too, so installationĪnd maintenance of them will depend on the route you choose. To install and use these Docker images, you'll need to keep the above in mind while following their documentation. 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). Your Series would be in /data/tv, torrents in /data/downloads/torrents and/or usenet downloads in /data/downloads/usenet. But I recommend adapting these instructions. That would be from the Web GUI, very simple once you find where. The best solution is to use a single, common volume inside the containers, Indexers are setup inside of Sonarr and Radarr. 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. I do understand that this is primarily a Kodi problem, since the information is in the tvshow.nfo and they just seem to not use it.Most docker containers use /config volume to mount the data directory and supply that path to Sonarr as parameter. Which would remove the possibility to use the scrappers for specific other options, what Sonarr is not offering. The alternative is obviously to select "episode metadata" and turn of scapping on Kodi all together. All the information should be available since its already included in the fields. if activate write the episodeguide information as json format.add a option to decide whether the episodeguide information should be written or not.Since the metadata section is specifically focused on Kodi it would make sense to The scrapper developers have agreed to advance the to a json format: Describe the solution you'd like (tvdb, moviedb, etc.) This was also the reason to get rid of it in the first place. With v19 this is no longer possible, because the tvshow.nfo file does not contain an element, which is the info passed to the scapper by Kodi.Īnd if the "episode metadata" flag is not set, Kodi will not load any episodes into its database.įurthermore, the information has been flawed for quite a while because of the different episode sources. let Kodi scrap the individual episodes of this show.Until v19 the following scenario was doable: Sonarr is not writing this at all (and with good reason - #4448) Since Kodi v19 they are apparently relying heavily on the field in the NFO file. Is your feature request related to a problem? Please describe I have searched the existing open and closed issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |