docker.recipes

Lidarr Music Manager

intermediate

Music collection manager for Usenet and BitTorrent users.

Overview

Lidarr is an automated music collection manager designed for Usenet and BitTorrent users, built as a fork of Sonarr specifically for music libraries. It monitors multiple RSS feeds for new releases from your favorite artists, automatically searches for and downloads music files, then organizes them with proper naming conventions and metadata. Lidarr integrates with popular download clients like SABnzbd, NZBGet, qBittorrent, and Transmission while fetching comprehensive metadata from MusicBrainz and Last.fm to ensure your music collection maintains consistency and quality. This containerized deployment leverages the LinuxServer.io image which provides automatic updates, proper file permissions handling, and optimized configuration management. The setup includes dedicated volumes for configuration persistence and separate mount points for your music library and download directories, enabling Lidarr to monitor completed downloads and automatically move files to your organized music collection. The isolated network configuration ensures secure communication while maintaining access to external indexers and metadata providers. This stack is ideal for music enthusiasts managing large digital collections, home media server administrators, and users seeking to automate their music acquisition workflow. The combination of Lidarr's intelligent release monitoring with Docker's portability makes it perfect for NAS deployments, dedicated media servers, and cloud-based setups where consistent music library management across different environments is essential.

Key Features

  • Automatic music release monitoring with calendar view showing upcoming and missing releases
  • MusicBrainz integration for comprehensive artist, album, and track metadata management
  • Quality profile management supporting different audio formats (FLAC, MP3, AAC) with bitrate preferences
  • Artist and album search with manual and automatic release selection capabilities
  • Import list support for Last.fm, Spotify playlists, and MusicBrainz collections
  • Advanced renaming engine with customizable folder structures and file naming patterns
  • Download client integration with completed download handling and failed download management
  • Indexer management supporting both Usenet and torrent sources with category filtering

Common Use Cases

  • 1Home media server operators building comprehensive digital music libraries with automated acquisition
  • 2Audiophiles maintaining high-quality music collections with specific format and bitrate requirements
  • 3Music collectors tracking discographies and automatically downloading new releases from favorite artists
  • 4NAS users centralizing music management across multiple devices and streaming applications
  • 5Media enthusiasts integrating with Plex, Jellyfin, or Emby servers for automated library updates
  • 6Users migrating from manual music downloading to automated workflow management
  • 7Music discovery enthusiasts importing Spotify playlists and Last.fm recommendations for automated downloads

Prerequisites

  • Minimum 2GB RAM and 10GB storage space for application data and temporary processing
  • Access to Usenet providers or private/public torrent trackers for content acquisition
  • Download client (SABnzbd, NZBGet, qBittorrent, Transmission) configured and accessible
  • Network access to port 8686 for web interface and API communication
  • Proper user permissions (PUID/PGID) matching your system's file ownership requirements
  • Indexer accounts or API keys for automated search capabilities across content sources

For development & testing. Review security settings, change default credentials, and test thoroughly before production use. See Terms

docker-compose.yml

docker-compose.yml
1services:
2 lidarr:
3 image: lscr.io/linuxserver/lidarr:latest
4 container_name: lidarr
5 environment:
6 - PUID=1000
7 - PGID=1000
8 - TZ=UTC
9 volumes:
10 - lidarr-config:/config
11 - /path/to/music:/music
12 - /path/to/downloads:/downloads
13 ports:
14 - "8686:8686"
15 networks:
16 - lidarr-network
17 restart: unless-stopped
18
19volumes:
20 lidarr-config:
21
22networks:
23 lidarr-network:
24 driver: bridge

.env Template

.env
1# Lidarr
2# Change paths to your directories

Usage Notes

  1. 1Web UI at http://localhost:8686
  2. 2Add indexers and download clients
  3. 3Search and download music
  4. 4Automatic organization
  5. 5Metadata fetching

Quick Start

terminal
1# 1. Create the compose file
2cat > docker-compose.yml << 'EOF'
3services:
4 lidarr:
5 image: lscr.io/linuxserver/lidarr:latest
6 container_name: lidarr
7 environment:
8 - PUID=1000
9 - PGID=1000
10 - TZ=UTC
11 volumes:
12 - lidarr-config:/config
13 - /path/to/music:/music
14 - /path/to/downloads:/downloads
15 ports:
16 - "8686:8686"
17 networks:
18 - lidarr-network
19 restart: unless-stopped
20
21volumes:
22 lidarr-config:
23
24networks:
25 lidarr-network:
26 driver: bridge
27EOF
28
29# 2. Create the .env file
30cat > .env << 'EOF'
31# Lidarr
32# Change paths to your directories
33EOF
34
35# 3. Start the services
36docker compose up -d
37
38# 4. View logs
39docker compose logs -f

One-Liner

Run this command to download and set up the recipe in one step:

terminal
1curl -fsSL https://docker.recipes/api/recipes/lidarr-music-manager/run | bash

Troubleshooting

  • Permission denied errors accessing music or download folders: Verify PUID and PGID environment variables match your system user and group IDs
  • Lidarr cannot connect to download clients: Ensure download client host addresses use container names or proper IP addresses within the Docker network
  • Missing or incorrect metadata for imported music: Check MusicBrainz connectivity and consider manual album matching for ambiguous releases
  • Downloads not moving to music folder: Verify download client category settings match Lidarr configuration and folder paths are correctly mapped
  • Web interface shows 'Application Offline': Check container logs for port conflicts or configuration file corruption in the config volume
  • Indexer searches returning no results: Verify API keys are valid and indexer URLs are accessible from within the container network

Community Notes

Loading...
Loading notes...

Download Recipe Kit

Get all files in a ready-to-deploy package

Includes docker-compose.yml, .env template, README, and license

Ad Space