1 Avoid common pitfalls
    Volumes and Paths

    There are two common problems with Docker volumes: Paths that differ between the Lidarr and download client container and paths that prevent fast moves and hard links.
    The first is a problem because the download client will report a download's path as /torrents/My.Music.2018/, but in the Lidarr container that might be at /downloads/My.Music.2018/. The second is a performance issue and causes problems for seeding torrents. Both problems can be solved with well planned, consistent paths.

    Most Docker images suggest paths like /musics and /downloads. This causes slow moves and doesn't allow hard links because they are considered two different file systems inside the container. Some also recommend paths for the download client container that are different from the Lidarr container, like /torrents.
    The best solution is to use a single, common volume inside the containers, such as /data. Your Musics would be in /data/Musics, torrents in /data/downloads/torrents and/or usenet downloads in /data/downloads/usenet.

    If this advice is not followed, you may have to configure a Remote Path Mapping in the Lidarr web UI (Settings › Download Clients).
    Ownership and Permissions

    Permissions and ownership of files is one of the most common problems for Lidarr users, both inside and outside Docker. Most images have environment variables that can be used to override the default user, group and umask, you should decide this before setting up all of your containers. 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.
    Keep in mind that Lidarr will need read and write to the download folders as well as the final folders.

    For a more detailed explanation of these issues, see The Best Docker Setup and Docker Guide wiki article.