![]() Sonarr does not regularly search for episode files that are missing or have not met their quality goals.Read about how to configure Sonarr here.¶ Sonarr Basics ¶ How does Sonarr find episodes? Now that the setup is complete, click ‘ok’ and the container will launch. It’s also a good idea to input the local timezone, as many containers need this to run. Put the IDs from the SSH session into the Environment tab as shown below. The command for obtaining the UID and GID in this case was id automation. We setup a user named automation to run the containers. Once logged in type id to show your UID (aka PUID) and the GID (aka PGID) for the selected user. You will not be able to see the password as you type it. To obtain the Personal User ID (PUID) and Personal Group ID (PGID) of the user that will be running the container, use Putty or an equivalent program to SSH into your NAS.Įnter the IP address of your NAS in Putty, select the SSH radio button, and click Open.Įnter the admin login information for the NAS. The purpose of this is so that in the event the container is compromised, the entire NAS will not be accessible. This user needs read/write privileges to the Docker’s /config directory as well as the /Media directory. It is good practice to create a new user that is used exclusively for running the container. For the container to run properly and to access and modify the directories, it must be given user permissions. ![]() If this is not done, your machine may use a random port each time and cause confusion.Įnvironment is where variables are set that are needed to allow the container to run. Local Port needs to be changed from Auto to the matching Container Port. This should be left to the default value since Sonarr will be looking for this port. Port settings are used to open the container within a browser. Use /config to mount the folder for Sonarr’s configuration files, and /Media to mount the folder which contains the Downloads and Library sub directories. (DO NOT use this method)Ĭlick Add Folder to begin mounting each path. The old method used multiple BTRFS shares, and therefore multiple file systems. Because of this, copy + move does not execute properly across the different file systems. On a Synology, each share is a BTRFS sub-volume and acts as a different file system. This is so that the Usenet client can move files instantly and the torrent client can use hard links, as to not waste space while simultaneously leaving the torrent’s copy to seed in the /completed folder until X ratio is met. It is important to setup the folders in such a way that the Download folder is a sub folder alongside the Library folder. ![]() These folders all need to be created prior to setting up the container so that they can be browsed to and mounted. Use your servers IP address followed by the container’s port number 8989. Within the Advanced Settings, enable auto-restart, and create a shortcut on desktop (if that interests you). Start out by giving the container a name and then clicking Advanced Settings. Launch the container to begin configuring it. ![]() Once you find the one you would like, select it and click download it.Īfter it’s done downloading, it will move into the Image tab. We prefer LinuxServer’s automatic builds. Once Docker has been installed, run it and navigate to the registry tab to search for Sonarr. Once that resource has been added, search the package center for Docker. If you’re on a Synology device, this can be done by going to Package Center > Settings > Package Sources and adding. Setting up Sonarr is really simple once you have Docker installed.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |