Skip to content

Lidarr in Docker on a Synology NAS

UpdateDate
New guide released19/09/2021
Added Docker-Compose and updated wording15/12/2021


What is Lidarr?

Lidarr is used to search, download and organise your Music in conjunction with your preferred Usenet or Torrent downloaders and indexers.

Lets Begin

In this guide I will take you through the steps to get Lidarr up and running in Docker.

In order for you to successfully use this guide please complete the two preceding guides

Downloading the Lidarr Image

Open up Docker within DSM and navigate to the ‘Registry’ tab, then search for ‘Lidarr’.

In the list of available containers select the one made by Linuxserver as shown below, right click on it and select ‘Download’ or click the button at the top of the window.

When the dialogue pops up asking you to choose a version, make sure you choose ‘Latest’ from the list.

You can check the status of the download over on the ‘Image’ tab, it will take a few minutes depending on the speed of your internet connection.

Setting up the container

In Docker click on the ‘Image’ tab, in the list of your containers select the ‘Linuxserver/Lidarr’ image and click on ‘Launch’

You will now see the initial setup screen, if you want to you can change the name of the container to something else.

If you are using a number of services on a machine with a limited amount of memory or lower powered CPU you can also set up resource limitations, but this is generally not required.

You will also notice a Configure capabilities button — don’t change anything in here!

Next up we are going to click on the ‘Advanced Settings’ button, this will take you to a new window with a number of tabs which we are going to work through.

On the first tab enable ‘Auto Restart’ this will ensure Lidarr will automatically start up whenever you reboot your NAS.

Volumes / Mounts

We can now move onto the volume tab in which we will be specifying the directories where Lidarr will store its configuration files and where to find our media and downloads

Click on Add Folder, click on the ‘docker’ folder and create a new sub-folder called ‘lidarr’ select this folder and click ‘select’

You will now need to enter /config into the ‘Mount path’

Now click Add Folder again and this time select the top level ‘data’ folder and click Select.

Next you will need to enter /data into ‘Mount path’ and your settings should look like the table/screenshot below

File/FolderMount path
docker/lidarr/config
data/data

Network

We are not going to be specifying specific ports for Lidarr to use as we want to keep things simple, tick the ‘Use the same network as Docker Host’

You do not need to set up anything on these tabs.

Environment Variables (PGID,  PUID and Timezone)

Next we are going to set up a couple of environment variables that docker will use to allow the container access to our files and folders and also to tell it where we live in the world.

Click the Add button, and fill in the following details as per the table/screenshot, you will need to do one at a time.

variableValue
PUIDThe UID you obtained in the user setup guide
PGIDThe GID you obtained in the user setup guide
TZYour timezone wikipedia.org/wiki/List_of_tz_database_time_zones

Almost Done

You have now completed the setup of the container.

Click on Apply to move back to the initial settings screen and then click next, you will be shown an overall summary of the settings we have specified, this is a good time to double-check everything is correct. Finally, click on Done and the container should start to boot.

You should now be able to access Lidarr via the IP of your NAS followed by the port 8686

e.g 192.168.0.40:8686

Make sure you check out page 2 of this guide that covers some common basic settings.

Docker Compose

You can use the below code saved as lidarr.yml in the ‘/docker/lidarr’ share, this will do the entire process above in one quick command via SSH. Ensure you change the variables to your own.

version: "3.8"
services:
  linuxserver-lidarr:
    image: linuxserver/lidarr:latest
    container_name: lidarr
    environment:
      - PUID=YOURUID
      - PGID=YOURGID
      - TZ=YOURTIMEZONE
    volumes:
      - /volume1/data:/data
      - /volume1/docker/lidarr:/config
    network_mode: host
    restart: unless-stopped
sudo docker-compose -f /volume1/docker/lidarr/lidarr.yml up -d


Throw me some bits or buy me a coffee?

If you have found my site useful please consider pinging me a tip as it helps cover the cost of running the site, you can even buy me a coffee 🙂

Buy Me A Coffee
Doge / Ethereum / Bitcoin

Pages: 1 2

Published inDockerSynology

2 Comments

  1. NeilM NeilM

    Thank you as always.

    So, a couple of comments for maybe a future article.

    When I create a docker container, I like to use the as part of the docker name, the version of the application/docker image.

    In the case of lidarr – lidarr-0.8.1.2135

    I would store under the lidarr folder in configs, I would create a specific version of the config, ready for 0.8.1.2135.

    I wouldn’t grab the latest image, I would grab the version that corresponded to latest. That way in my image folder I would have “Version-0.8.1.2135”

    So, when I come to upgrade, I take a copy of the config, Version-0.8.1. 2135, and drop that into a folder called “Version.0.9.1.0001”. This give the user a backup container with a fully working version of lidarr, which they can go back to, if the newer version blows up.

    Also, when it comes to delete older images and containers, they are all identifiable by the fact they all share the same version number, from config->image>container.

    I tend to export the container information to the JSON file, modify that, and then import that to create the new container. Remembering to switch off the auto start on the previous version of the container.

    • Dr_Frankenstein Dr_Frankenstein

      Thanks Neil, I try and keep the guides at a super easy to work with level, so aimed at newer users. This adds a layer of complexity but makes sense why you would do its this way.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

drfrankenstein.co.uk – writing Synology Docker Guides since 2016 – Join My Discord!