Note: Raspberry Pi OS and Raspbian are both flavors of Debian
For the Debian / Ubuntu / Raspbian beginners there isn't an Apt Repository or Deb package.
If you want an easy life, follow this community provided and maintained Easy Install script for a base Debian (Raspbian / Raspberry Pi OS) / Ubuntu install.
For the official installation instructions that are 'Hands on' follow the Debian / Ubuntu Hands on Install steps further below.
Please see the *Arr Community Installation Script
It is assumed you have a basic knowledge of linux or the ability to google / learn as necessary. Otherwise it is suggested to use an OS you know and understand
You'll need to install the binaries using the below commands.
The steps below will download Lidarr and install it into
/opt
Lidarr will run under the userlidarrand groupmedia
Lidarr's configuration files will be stored in/var/lib/lidarr
sudo apt install curl mediainfo sqlite3 libchromaprint-tools
Warning: Ignoring the below prerequisites will result in a failed installation and non-functional application.
Installation Prerequisites
The below instructions are based on the following prerequisites. Change the instructions as needed to suit your specific needs if necessary.
* The userlidarris created
* The userlidarris part of the groupmedia
* Your download clients and media server run as and are a part of the groupmedia
* Your paths used by your download clients and media server are accessible (read/write) to the groupmedia
* You created the directory/var/lib/lidarrand ensured the userlidarrhas read/write permissions for it
By continuing below, you acknowledge that you have read and met the above requirements.
dpkg --print-architecture
arch=x64arch=armarch=arm64wget --content-disposition 'http://lidarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64'
tar -xvzf Lidarr*.linux*.tar.gz
/opt/sudo mv Lidarr/ /opt
This assumes you have created the user and will run as the user
lidarrand groupmedia. You may change this to fit your usecase. It's important to choose these correctly to avoid permission issues with your media files. We suggest you keep at least the group name identical between your download client(s) and Lidarr.
sudo chown -R lidarr:media /opt/Lidarr
The below systemd creation script will use a data directory of
/var/lib/lidarr. Ensure it exists or modify it as needed. For the default data directory of/home/$USER/.config/Lidarrsimply remove the-dataargument. Note: that$USERis the User Lidarr runs as and is defined below.
cat << EOF | sudo tee /etc/systemd/system/lidarr.service > /dev/null
[Unit]
Description=Lidarr Daemon
After=syslog.target network.target
[Service]
User=lidarr
Group=media
Type=simple
ExecStart=/opt/Lidarr/Lidarr -nobrowser -data=/var/lib/lidarr/
TimeoutStopSec=20
KillMode=process
Restart=on-failure
[Install]
WantedBy=multi-user.target
EOF
sudo systemctl -q daemon-reload
sudo systemctl enable --now -q lidarr
rm Lidarr*.linux*.tar.gz
Typically to access the Lidarr web GUI browse to http://{Your server IP Address}:8686
If Lidarr did not appear to start, then check the status of the service:
sudo journalctl --since today -u lidarr
If Lidarr v3+ fails to start on older end-of-life systems (Debian 10, Debian 11, Synology DSM, Ubuntu 18, Ubuntu 20) due to SQLite/GLIBC compatibility issues, see the SQLite version workaround below.
To uninstall and purge:
Warning: This will destroy your application data.
sudo systemctl stop lidarr
sudo rm -rf /opt/Lidarr
sudo rm -rf /var/lib/lidarr
sudo rm -rf /etc/systemd/system/lidarr.service
sudo systemctl -q daemon-reload
To uninstall and keep your application data:
sudo systemctl stop lidarr
sudo rm -rf /opt/Lidarr
sudo rm -rf /etc/systemd/system/lidarr.service
sudo systemctl -q daemon-reload
This workaround is only for older end-of-standard-support systems with outdated GLIBC / SQLite. It is not a fix for SQLite corruption errors — those have a completely different recovery path; see FAQ → Database disk image is malformed.
Lidarr v3 and later uses a bundled SQLite build that requires newer GLIBC than ships with end-of-standard-support distributions. Affected systems include Debian 10, Debian 11, Ubuntu 18.04, Ubuntu 20.04, and some Synology DSM versions. If Lidarr fails to start with SQLite initialisation errors (as opposed to corruption errors), you can force it to link against the distribution's own SQLite library instead.
Symlink the system SQLite library into Lidarr's install directory under the name Lidarr expects:
# First, ensure libsqlite3-0 is installed (not just sqlite3):
sudo apt update
sudo apt install libsqlite3-0
# Navigate to Lidarr installation directory
cd /opt/Lidarr/
# Backup the bundled library
mv libe_sqlite3.so libe_sqlite3.so.backup 2>/dev/null || true
# Create the symlink. The library path depends on your architecture:
# - amd64/x64: /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
# - arm64: /usr/lib/aarch64-linux-gnu/libsqlite3.so.0
# - armhf: /usr/lib/arm-linux-gnueabihf/libsqlite3.so.0
# For amd64:
ln -s /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 libe_sqlite3.so
# Verify the symlink
ls -la libe_sqlite3.so
Restart Lidarr after creating the symlink.
Every Lidarr update replaces the files in
/opt/Lidarr/, so the symlink has to be recreated after each update. If you're using this workaround, script the symlink into your update procedure.