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.Book/, but in the Readarr 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 Readarr and download client container and paths that prevent fast moves and hard links. These instructions provide generic guidance that should apply to any Readarr Docker image. ![]() However, a number of third parties have created and maintain their own. The Readarr team does not offer an official Docker image.
0 Comments
Leave a Reply. |