The Lidarr team only provides builds for FreeBSD. The FreeBSD community maintains Plugins and Ports.
The FreeBSD community also maintains installation instructions, and anyone with a GitHub account may update the wiki as needed.
From the main screen select Jails
Click ADD
Click Advanced Jail Creation
Name (any name will work): Lidarr
Jail Type: Default (Clone Jail)
Release: 12.2-Release (or newer)
Configure Basic Properties to your liking
Configure Jail Properties to your liking but add:
allow_raw_socketsis helpful for troubleshooting (for example, ping, traceroute) but isn't needed.
Configure Network Properties to your liking
Configure Custom Properties to your liking
Click Save
After the jail starts, set one more property so Lidarr can see the storage space of your mounted media locations. Open a root shell on the server and run:
iocage stop <jailname>
iocage set enforce_statfs=1 <jailname>
iocage start <jailname>
Back on the jails list, find your newly created jail for lidarr and click Shell.
To install Lidarr:
- Ensure your pkg repo pulls packages from
/latestand not/quarterly- Check
/usr/local/etc/pkg/repos/FreeBSD.conf- If that file doesn't exist, copy
/etc/pkg/FreeBSD.confto that location, open it, and replacequarterlywithlatest
pkg install lidarr
Don't close the shell yet — a few more steps remain.
The built-in updater is off by default. The pkg-message gives instructions on how to turn it on, but be aware: enabling it can break pkg check -s and pkg remove for Lidarr when the updater replaces files.
To enable the service:
sysrc lidarr_enable=TRUE
If you don't want to run under user/group lidarr, tell the service file which user/group to use:
sysrc lidarr_user="USER_YOU_WANT"
sysrc lidarr_group="GROUP_YOU_WANT"
lidarr stores its data, config, logs, and PID files in /usr/local/lidarr by default. The service file creates this directory and takes ownership of it only if it doesn't exist. To store these files elsewhere (for example, a dataset mounted into the jail for easier snapshots), change the path using sysrc:
sysrc lidarr_data_dir="DIR_YOU_WANT"
If you use an existing location, manually change ownership to the UID/GID lidarr uses, or add lidarr to a GID that has write access.
Start the service:
service lidarr start
If everything went according to plan, Lidarr should be running on the IP of the jail (port 8686).
You can now close the shell.
The service appears to be running but the UI isn't loading or the page is timing out
allow_mlock is on in the jailSystem.NET.Sockets.SocketException (43): Protocol not supported
VNET turned on for your jail, ip6=inherit, or ip6=newThe service script works around the lack of VNET and/or IP6, so VNET or ip6=inherit isn't required.