![]() ![]() If this advice is not followed, you may have to configure a Remote Path Mapping in the Radarr web UI (Settings › Download Clients). The best solution is to use a single, common volume ![]() Some also recommend paths for the download client container that are different from the Radarr container, like ![]() This causes slow moves and doesn't allow hard links because theyĪre considered two different file systems Both problems can be solved with well planned, consistent paths. The second is a performance issue and causes problems for seeding torrents. torrents/My.Movie.2018/, but in the Radarr container that might be at The first is a problem because the download client will report a download's path as There are two common problems with Docker volumes: Paths that differ between the Radarr and download client container and paths that prevent fast moves and hard links. Radarr v4 will convert the given directory on startup if a Radarr v0.2 or v3 database is found. Volume to mount the data directory and supply that path to Radarr as parameter. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |