# Binhex lidarr

Binhex lidarr is a self-hosted downloaders app. Lidarr is a music collection manager for Usenet and BitTorrent users that monitors RSS feeds, downloads and renames new releases, and upgrades existing files to maintain a high-quality music library. It is open source and self-hosted, installable on Docker Hub, TrueNAS and Proxmox.

Canonical page: https://ourlocalhost.com/app/5995/binhex-lidarr

## Description

Lidarr is a music collection manager for Usenet and BitTorrent users that monitors RSS feeds, downloads and renames new releases, and upgrades existing files to maintain a high-quality music library.

## Platform availability

Available on 2 of 10 platforms: TrueNAS, Proxmox.

## Health score

58/100 (Fair), based on 5 of 5 factors.
- Maintained: 72 (last commit 9 days ago)
- Popular: 20 (9 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Light to run: 95 (512 MB minimum RAM, runs on ARM)
- Security check: 85 (no serious findings, CI)

## Links

- GitHub: https://github.com/binhex/arch-lidarr
- Docker Hub: https://hub.docker.com/r/binhex/arch-lidarr
- TrueNAS: https://apps.truenas.com/catalog/lidarr
- Proxmox: https://community-scripts.github.io/ProxmoxVE/scripts?id=lidarr

## Common questions

### What port should I expose for binhex Lidarr?

Expose container port 8686 and access the app on that host port.

### Which volumes should I mount for config, music, and downloads?

Mount a persistent directory to /config for settings, /media for your music library, and /data for a watched download folder.

### How should I set PUID and PGID in the binhex Lidarr container?

Set PUID and PGID to the host user and group that should own the files. You can find those values on the host with the id command.

### How do I avoid path mapping problems between Lidarr and a download client?

Use the same absolute paths inside the Lidarr and download client containers for shared music and download locations. Mismatched paths cause import issues, and paths that prevent fast moves or hard links can also cause problems.

### What should I do if Lidarr uses 100% CPU after a few hours?

Users have reported Lidarr reaching 100% CPU after one to 24 hours of uptime, even when the container logs show no errors.

### Which Lidarr build fixes the album list bug mentioned in the support thread?

Lidarr build 281 or newer fixes a bug that affects working with album lists. The binhex image is built from the latest Arch Linux AUR development build.

---
Source: Our Local Host (https://ourlocalhost.com/app/5995/binhex-lidarr), the self-hosted and open-source app directory.
