
We’ll use default 755 permissions for all datasets. Navigate to Storage → Pools and add the datasets and permissions. Navigate to Accounts → Users and add the following users. Navigate to Accounts → Groups and add the following groups.
E.g., Radarr can only read ( ro) from the torrent dataset but write ( rw) to the movies dataset.
Jails share media datasets, but only one user has write permissions. Each jail owns a dataset for configuration data. Each service inside the jail runs as a different user. Each service lives inside a separate jail. The diagram above translates to the following requirements: For hardlinking to work, the torrent client and *arrs must share the same dataset and jail mount points. Note that using hardlinks with the *arrs doesn’t work with this setup. I use DHCP reservations to manage my server IPs, so I use the dhcp=1 option to create jails. I’ll only cover options that deviate from the defaults. See also: Legal issues with BitTorrent (Wikipedia) Disclaimerįrom Wikipedia on BitTorrent Legislation:Īlthough the protocol itself is legal, problems stem from using the protocol to traffic copyright infringing works, since BitTorrent is often used to download otherwise paid content, such as movies and video games. The FN11.3 iocage jails - Plex, Tautulli, Sonarr, Radarr, Lidarr, Jackett, Transmission, Organizr guide inspired me to write this guide. #Sonarr config file install
This post documents the steps required to install qBittorrent, Jackett, Lidarr, Radarr, Sonarr, and Plex in TrueNAS jails version 12.0-U6.