Lidarr in Autopirate Docker Swarm stack

Get your FREE "elfhosted" Lidarr instance for demo / trial

Want to see a live demo, or "kick the tyres" before you commit to self-hosting Lidarr?

Try out an "ElfHosted" instance of Lidarr for FREE!

Warning

This is not a complete recipe - it's a component of the autopirate "uber-recipe", but has been split into its own page to reduce complexity.

Lidarr is an automated music downloader for NZB and Torrent. It performs the same function as Headphones, but is written using the same(ish) codebase as Radarr and Sonarr. It's blazingly fast, and includes beautiful album/artist art. Lidarr supports SABnzbd, NZBGet, Transmission, µTorrent, Deluge and Blackhole (just like Sonarr / Radarr)

Lidarr Screenshot

Inclusion into AutoPirate

To include Lidarr in your AutoPirate stack, include something like the following example in your autopirate.yml docker-compose stack definition file:

  lidarr:
    image: lscr.io/linuxserver/lidarr:latest
    env_file: /var/data/config/lidarr/lidarr.env
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/data/media:/media
      - /var/data/lidarr:/config
    deploy:
      replicas: 1
      labels:
        # traefik
        - traefik.enable=true
        - traefik.docker.network=traefik_public

        # traefikv1
        - traefik.frontend.rule=Host:lidarr.example.com
        - traefik.port=8686
        - traefik.frontend.auth.forward.address=http://traefik-forward-auth:4181
        - traefik.frontend.auth.forward.authResponseHeaders=X-Forwarded-User
        - traefik.frontend.auth.forward.trustForwardHeader=true        

        # traefikv2
        - "traefik.http.routers.lidarr.rule=Host(`lidarr.example.com`)"
        - "traefik.http.routers.lidarr.entrypoints=https"
        - "traefik.http.services.lidarr.loadbalancer.server.port=8686"
        - "traefik.http.routers.lidarr.middlewares=forward-auth"

Fast-track with premix! 🚀

I automatically and instantly share (with my sponsors) a private "premix" git repository, which includes necessary docker-compose and env files for all published recipes. This means that sponsors can launch any recipe with just a git pull and a docker stack deploy 👍.

🚀 Update: Premix now includes an ansible playbook, so that sponsors can deploy an entire stack + recipes, with a single ansible command! (more here)

Assemble more tools..

Continue through the list of tools below, adding whichever tools your want to use, and finishing with the end section:

Lidarr vs Headphones

Lidarr and Headphones perform the same basic function. The primary difference, from what I can tell, is that Lidarr is build on the Arr stack, and so plays nicely with Prowlarr.

Integrate Lidarr with Beets

I've not tried this yet, but it seems that it's possible to integrate Lidarr with Beets

Chef's notes 📓

In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition. ↩

Did you receive excellent service? Want to compliment the chef? (..and support development of current and future recipes!) Sponsor me on Github / Ko-Fi / Patreon, or see the contribute page for more (free or paid) ways to say thank you! 👏

Employ your chef (engage) 🤝

Is this too much of a geeky PITA? Do you just want results, stat? I do this for a living - I'm a full-time Kubernetes contractor, providing consulting and engineering expertise to businesses needing short-term, short-notice support in the cloud-native space, including AWS/Azure/GKE, Kubernetes, CI/CD and automation.

Learn more about working with me here.

Want to know now when this recipe gets updated, or when future recipes are added? Subscribe to the RSS feed, or leave your email address below, and we'll keep you updated.