You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
LinuxServer-CI dbfd384f93 Bot Updating Package Versions 6 days ago
.github Rebase to Alpine 3.15 2 months ago
root Rebase to focal 3 months ago
.dockerignore first save up 5 years ago
.editorconfig Bot Updating Templated Files 1 year ago
.gitignore Bot Updating Templated Files 2 years ago
Dockerfile Remove alpine warning message 2 months ago
Dockerfile.aarch64 Remove alpine warning message 2 months ago
Dockerfile.armhf Remove alpine warning message 2 months ago
Jenkinsfile Rebase to Alpine 3.15 2 months ago
LICENSE Bot Updating Templated Files 3 years ago Rebase to Alpine 3.15 2 months ago
jenkins-vars.yml Rebase to Alpine 3.15 2 months ago
package_versions.txt Bot Updating Package Versions 6 days ago
readme-vars.yml Rebase to Alpine 3.15 2 months ago

Blog Discord Discourse Fleet GitHub Open Collective

The team brings you another container release featuring:

  • regular and timely application updates
  • easy user mappings (PGID, PUID)
  • custom base image with s6 overlay
  • weekly base OS updates with common layers across the entire ecosystem to minimise space usage, down time and bandwidth
  • regular security updates

Find us at:

  • Blog - all the things you can do with our containers including How-To guides, opinions and much more!
  • Discord - realtime support / chat with the community and the team.
  • Discourse - post on our community forum.
  • Fleet - an online web interface which displays all of our maintained images.
  • GitHub - view the source for all of our repositories.
  • Open Collective - please consider helping us by either donating or contributing to our budget

linuxserver/lidarr pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Docker Pulls Docker Stars Jenkins Build LSIO CI

Lidarr is a music collection manager for Usenet and BitTorrent users. It can monitor multiple RSS feeds for new tracks from your favorite artists and will grab, sort and rename them. It can also be configured to automatically upgrade the quality of files already downloaded when a better quality format becomes available.


Supported Architectures

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Architecture Available Tag
x86-64 amd64-<version tag>
arm64 arm64v8-<version tag>
armhf arm32v7-<version tag>

Version Tags

This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.

Tag Available Description
latest Stable Lidarr releases.
develop Develop Lidarr Releases.
nightly Nightly Lidarr Releases.

Application Setup

Access the webui at <your-ip>:8686, for more information check out Lidarr.

Special Note: Following our current folder structure will result in an inability to hardlink from your downloads to your Music folder because they are on seperate volumes. To support hardlinking, simply ensure that the Music and downloads data are on a single volume. For example, if you have /mnt/storage/Music and /mnt/storage/downloads/completed/Music, you would want something like /mnt/storage:/media for your volume. Then you can hardlink from /media/downloads/completed to /media/Music.

Another item to keep in mind, is that within lidarr itself, you should then map your download client folder to your lidarr folder: Settings -> Download Client -> advanced -> remote path mappings. I input the host of my download client (matches the download client defined) remote path is /downloads/Music (relative to the internal container path) and local path is /media/downloads/completed/Music, assuming you have folders to seperate your downloaded data types.

Media folders

We have set /music and /downloads as optional paths, this is because it is the easiest way to get started. While easy to use, it has some drawbacks. Mainly losing the ability to hardlink (TL;DR a way for a file to exist in multiple places on the same file system while only consuming one file worth of space), or atomic move (TL;DR instant file moves, rather than copy+delete) files while processing content.

Use the optional paths if you dont understand, or dont want hardlinks/atomic moves.

The folks over at wrote a good write-up on how to get started with this.


Here are some example snippets to help you get started creating a container.

version: "2.1"
    container_name: lidarr
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
      - /path/to/appdata/config:/config
      - /path/to/music:/music #optional
      - /path/to/downloads:/downloads #optional
      - 8686:8686
    restart: unless-stopped

docker cli (click here for more info)

docker run -d \
  --name=lidarr \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/London \
  -p 8686:8686 \
  -v /path/to/appdata/config:/config \
  -v /path/to/music:/music `#optional` \
  -v /path/to/downloads:/downloads `#optional` \
  --restart unless-stopped \


Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

Parameter Function
-p 8686 Application WebUI
-e PUID=1000 for UserID - see below for explanation
-e PGID=1000 for GroupID - see below for explanation
-e TZ=Europe/London Specify a timezone to use EG Europe/London.
-v /config Configuration files for Lidarr.
-v /music Music files (See note in Application setup).
-v /downloads Path to your download folder for music (See note in Application setup).

Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__PASSWORD=/run/secrets/mysecretpassword

Will set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file.

Umask for running applications

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.

User / Group Identifiers

When using volumes (-v flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id user as below:

  $ id username
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)

Docker Mods

Docker Mods Docker Universal Mods

We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

Support Info

  • Shell access whilst the container is running: docker exec -it lidarr /bin/bash
  • To monitor the logs of the container in realtime: docker logs -f lidarr
  • container version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}' lidarr
  • image version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}'

Updating Info

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

Via Docker Compose

  • Update all images: docker-compose pull
    • or update a single image: docker-compose pull lidarr
  • Let compose update all containers as necessary: docker-compose up -d
    • or update a single container: docker-compose up -d lidarr
  • You can also remove the old dangling images: docker image prune

Via Docker Run

  • Update the image: docker pull
  • Stop the running container: docker stop lidarr
  • Delete the container: docker rm lidarr
  • Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
  • You can also remove the old dangling images: docker image prune

Via Watchtower auto-updater (only use if you don't remember the original parameters)

  • Pull the latest image at its tag and replace it with the same env variables in one run:

    docker run --rm \
    -v /var/run/docker.sock:/var/run/docker.sock \
    containrrr/watchtower \
    --run-once lidarr
  • You can also remove the old dangling images: docker image prune

Note: We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.

Image Update Notifications - Diun (Docker Image Update Notifier)

  • We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.

Building locally

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone
cd docker-lidarr
docker build \
  --no-cache \
  --pull \
  -t .

The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static

docker run --rm --privileged multiarch/qemu-user-static:register --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.


  • 06.06.22: - Rebase master branch to Alpine 3.15.
  • 06.05.22: - Rebase master branch to Focal.
  • 06.05.22: - Rebase develop branch to Alpine.
  • 04.02.22: - Rebase nightly branch to Alpine, deprecate nightly-alpine branch.
  • 30.12.21: - Add nightly-alpine branch.
  • 01.08.21: - Add libchromaprint-tools.
  • 11.07.21: - Make the paths clearer to the user.
  • 18.04.21: - Switch latest tag to net core.
  • 25.01.21: - Publish develop tag.
  • 20.01.21: - Deprecate UMASK_SET in favor of UMASK in baseimage, see above for more information.
  • 18.04.20: - Removed /downloads and /music volumes from Dockerfiles.
  • 05.04.20: - Move app to /app.
  • 01.08.19: - Rebase to Linuxserver LTS mono version.
  • 13.06.19: - Add env variable for setting umask.
  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
  • 08.03.19: - Rebase to Bionic, use proposed endpoint for libchromaprint.
  • 26.01.19: - Add pipeline logic and multi arch.
  • 22.04.18: - Switch to beta builds.
  • 17.03.18: - Add ENV XDG_CONFIG_HOME="/config/xdg" to Dockerfile for signalr fix.
  • 27.02.18: - Use json to query for new version.
  • 23.02.18: - Initial Release.