#How to configure sonarr install
#How to configure sonarr update
#How to configure sonarr upgrade

Make a remote copy of the entire Sonarr folder just in case.Back up your sonarrv2 through the web interface.You should generally follow the following steps at your own risk. modified service files, overrides, etc.), you should make sure to run some extra steps before.

If you have toyed with the v2 Sonarr configuration and are not using the vanilla setup by swizzin (e.g. Please check the Downgrading chapter if you want to go back. It is not possible to have both v2 and v3 installed at the same time.Īn additional backup of the v2 configuration is created in /root/sonarrv2.bak/, which includes an internal Sonarr backup file triggered via API right before the installation. Please keep the v2 installed for optimal results.

#How to configure sonarr install

The install script for Sonarr v3 includes functionality to migrate and remove a v2 ( sonarr) installation. Once setup, sonarr will be available at the link Migrating from v2 Used to specify a non-master user which sonarr v3 will run as after the installation.Used to specify a non-master user which sonarr v2 might have ran under before for the migration and user-group adding.So under /volume1/docker you need to create a directory for each of your dockers, so they all have a nice separate area for storing permanent files (other than the mount for media files, that is permanent too ofcourse). In sonarr’s case, using the lsio dockers, this is indeed /config and it’s where sonarr will store its database etc. This is where the app stores data that needs to survive when the docker instance reboots or is upgraded.

The second mount will be /volume1/docker/ mounted as /config or however the docker image specifies it. Those are all not required by creating the single /data mount, and allow sonarr etc to perform file moves rather than slow copy them across different mounts. Most guides or the docker hub pages tell you to create /downloads and /tv mounts for example. Not any of the subfolders! The subfolder(s) the specific application needs, you have to select in the applications itself, starting from the /data mount.

#How to configure sonarr upgrade

you can either use the DSM docker gui to upgrade the image and rebuild the container, or SSH into the NAS and run the actual docker commands, or write a script, or use docker-compose, to do the same thingĬreate only one mount in each docker for media files, /data Which points to /volume1/data. Im not sure what its like in windows but there are multiple ways to do it in DSM.

#How to configure sonarr update

if your OS isnt running the right versions who cares, everything the app requires is in the imageĪnd is the update process (when new builds are released) the same as it would be in windows? it makes it super robust in that OS changes wont screw up the app, nor will app changes screw up the OS. I prefer docker just so i can isolate the app from the OS and the data. Im on DSM 6.2.1-23824 Update 4 and using docker so you should be fine. I assume there are no issues using the latest version on DSM? which method is the preferred method? Im running all of those on a DS2411+ with 3gb ram in docker and while its not exactly what youd call speedy, its not that slow either, and i dont have any issues with them.

Essentially i’d be moving everything over from windows to synology - Sonarr, Radarr, Jackett, Transmission, Sabnzbd, and the Plex server.