Binhex lidarr
Lidarr is a music collection manager for Usenet and BitTorrent users that monitors RSS feeds, downloads and renames new releases, and upgrades existing files…
Platform availability
Available on 2 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
58/100 Fair
- Maintained
- 72last commit 9 days ago
- Popular
- 209 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 95512 MB minimum RAM, runs on ARM
- Security check
- 85no serious findings, CI
- GitHub stars
- 9
- Open issues
- 1
- Last commit
- 2026-11-12
- Latest release
- 3.1.6.5079-2-01
- License
- GPL-3.0
- Activity
- rising
Checked 2 days ago - source: GitHub (binhex/arch-lidarr)
Resources & Compatibility
Minimum requirements: 512 MB RAM, 1 CPU core(s), 1 GB disk. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Soulseek port settings In the Soulseek settings, set listen_port to an open port or 0 to disable incoming connections. If you want other peers to send files to you, open that port on your network; otherwise they may not reach you. source
- Keep your music folder organized Seakarr expects files arranged by artist and album, like Artist/Album/track files. Keep that folder in a safe place or back it up, because it is where your downloaded music is stored. source
- Limit simultaneous peer connections max_peers controls how many Soulseek connections it uses at once, and each uses a small amount of memory. Leave it modest unless you know your system has room, so the app does not use too many resources. source
- Port and volume setup Expose port 8686 for the web UI and map /config, /data, and /media volumes in your Docker command. source
Fetched 42 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
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.
Answers sourced from forums.unraid.net, forums.unraid.net, github.com, lidarr.audio
Community
- which lidarr container? : r/unRAID - Reddit (reddit)
- [Support] binhex - Lidarr - Docker Containers - Unraid (forum)
- [Support] binhex - Lidarr - Page 7 - Docker Containers - Unraid (forum)
- Issues With Lidarr Mappings, Radarr + Sonarr are fine (reddit)
Collected 48 days ago - public community threads