Skip to content

Lidarr in Docker on a Synology NAS

UpdateDate
New guide released19/09/2021

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 proceeding guides

Downloading the Lidarr Image

Open up Docker within DSM and navigate to the ‘Registry’ tab and 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 asked make sure you choose ‘Latest’ from the list of available versions

You can check the status of the download over on the ‘Image’ tab.

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, or if you are using a number of services on a machine with a limited amount of memory or lower powered CPU you can also setup resource limitations, but this is generally not required.

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’

Links / Port Settings

You do not need to setup anything on these tabs.

Environment Variables (PGID,  PUID and Timezone)

Next we are going to setup 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 7878

e.g 192.168.0.40:8686

Docker Compose

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

coming soon
coming soon

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
  • Bitcoin
  • Ethereum
  • Tether
  • Xrp
  • Polkadot
  • Binance coin
  • Litecoin
  • Bitcoin cash
  • Dogecoin
  • Tron
  • Monero
  • Omisego
Scan to Donate Bitcoin to bc1qfznx5kxad9k9z5t9y79mkm9ukfexan9a6wrzl0

Donate Bitcoin to this address

Scan the QR code or copy the address below into your wallet to send some Bitcoin

Scan to Donate Ethereum to 0x162fc7781D3C6c6f27197A3A92567b5DAF258f19

Donate Ethereum to this address

Scan the QR code or copy the address below into your wallet to send some Ethereum

Scan to Donate Tether to 0x162fc7781D3C6c6f27197A3A92567b5DAF258f19

Donate Tether to this address

Scan the QR code or copy the address below into your wallet to send some Tether

Scan to Donate Xrp to rKGpNHetksTn4dgwgpiTkg8JM4uJ3J6pam

Donate Xrp to this address

Scan the QR code or copy the address below into your wallet to send some Xrp

Scan to Donate Polkadot to 153iRH61nXQZUXMveZxCmYyzjf1cWYVnxpHpfifoNchQuXbY

Donate Polkadot to this address

Scan the QR code or copy the address below into your wallet to send some Polkadot

Scan to Donate Binance coin to bnb14ye5rju74u5ythneaum2rjvp8eqep6wq8flghx

Donate Binance coin to this address

Scan the QR code or copy the address below into your wallet to send some Binance coin

Scan to Donate Litecoin to LfNfer3aSqLx4p8KfbbkT96ArXLXLDPxoD

Donate Litecoin to this address

Scan the QR code or copy the address below into your wallet to send some Litecoin

Scan to Donate Bitcoin cash to qrc7scd2drzsd7kywpsjfklvkmm26fqc2vd7uyvdx9

Donate Bitcoin cash to this address

Scan the QR code or copy the address below into your wallet to send some Bitcoin cash

Scan to Donate Dogecoin to DCwbNzfYHx22MDSyEVLWgfjxziYHtcgwAM

Donate Dogecoin to this address

Scan the QR code or copy the address below into your wallet to send some Dogecoin

Scan to Donate Tron to TL1Q3vY9mHnDMedHRyU8ERUAY8SzJ4FXiV

Donate Tron to this address

Scan the QR code or copy the address below into your wallet to send some Tron

Scan to Donate Monero to 45qwFr42XiA8egC5z2HdSQ2FzzP9VR1MvD5Sicg4EhGvdvTutx9GsF6DeU8DHAsTZy2ShBERjCB5rdy8iQ9CFnFu9Z6Adgw

Donate Monero to this address

Scan the QR code or copy the address below into your wallet to send some Monero

Scan to Donate Omisego to 0x162fc7781D3C6c6f27197A3A92567b5DAF258f19

Donate Omisego to this address

Scan the QR code or copy the address below into your wallet to send some Omisego

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.