Iocage create -n "sonarr" -p /tmp/pkg.json -r 11.2-RELEASE ip4_addr="vnet0|/" defaultrouter="" vnet="on" allow_raw_sockets="1" boot="on" Personally I mount the video filesystem as readonly inside the plex jail as I don't need to be able to delete media from inside plex as it is managed through other applications.Įcho '' > /tmp/pkg.json There are 2 sets of directions below based on if you require the plexpass version or not. On the iocage create command for each jail you MUST replace, with the correct values for your setup. If you find an issue with anything please make a post in the discussion thread for this resource.įor any jail below that has commands for iocage all commands should be run from the FreeNAS host. If anyone would like to see any changes let me know and I'll be happy to make them. Having the apps dataset and datasets under it made for easy snapshots of just the application config data and easy reinstalls of jails as to import data you would just need to mount the /config directory back into the new jail. I highly recommend reading this post to get a better idea on the numerous ways permissions can be done in jails to best fit your needs.
#Sonarr forums torrent
This setup assumes you have a video dataset, a torrent dataset and apps dataset that has a dataset under it for each application's configuration files owned by the user that it will run as.ĭetermining the best choice for permissions for the video and torrents dataset is up to you to decide based on your setup. Most of these apps have their own forums, github repos, etc, where you can get help for each application on its own. This should help guide you to getting these apps installed however I don't have specifics on settings for each as it may vary based on your usage requirements. I figured I'd try to give back to the community a bit and share the steps for each application.
#Sonarr forums how to
When I did that I made detailed notes on how to setup each application's base install from scratch. I decided I'd migrate all of my applications back to Jails as I had them before Corral as I found them easier to manage and less resource intensive on the system. I found coming back to FreeNAS 11 some of the applications such as Transmission and Plex began to choke and lockup with the same datasets shared under NFS in Docker containers running under Rancher. While these applications worked well in Corral as docker containers with datasets shared via 9PFS.
Like a number of people who may be in the same case I was in, I had gone to Corral for Docker Support. Please post in the thread so other people also assist. Which makes no sense to me because as you can see above the downloads folder is in /home/media also with the same ownership, group and permissions.I try to check this thread about every 2 weeks but I will not respond to PMs for support. Odd thing is if I mount a different folder, let’s say Downloads for example it works fine. Logs show that I have a permissions issue.
I’ll be honest, I have no idea where these configurations are stored because my home/media/.config/radarr folder is totally empty but it’s saving everything I do.įinally I want to mount my /tv directory bound to /media/tv in the Sonarr interfance and attempt to do so in Sonarr’s settings, but nothing happens. So while the container is running as media:media I can now access Sonarr and use the web client and make configuration changes. However I can get Sonarr running if I use the Media PID and Media GID. That actually blocks me fully from the media folder for some reason.
You’ll notice in my docker compose I’m using the Sonarr PID with the Media GID. I then run my docker-compose up -d to start the docker containers. I ran chown to make my media user and group the owner of the media folders chown -R media:media /home/media My folders are set up as follows /home/media/tv I now have a user with a PID of 1002 (sonarr) and a GID of 1001 (media). Next I added this user to my media group which the jackett/sonarr/plex/torrent services share. I know I have my permissions correct, so here’s my whole setup.įirst thing I did was create a sonarr user sudo useradd sonarr The only thing I can’t do that’s driving me absolutely insane is mount my media drive as the root folder in Sonarr, as I get a permissions issue. Sonarr is up and running fine, I can access the web interface and muck about with configurations. I’m new at this so forgive me if this has been answered elsewhere
0 kommentar(er)
