![]() Now you can run Sonarr by accessing the DOCKER tab, clicking on the Sonarr icon and clicking start. This will now download and set up the container. Once you have your settings done click done. Pointing it up a level to just the Downloads folder resolved that issue. I used to have it pointing to Downloads/Incoming but Sonarr failed to see any completed downloads. I have found that if you are too specific with the download folder Sonarr does not find completed downloads. Host Path 4 is the share that have set up for your downloader. This will be the share that we set up previously. Host Path 3 is the share you want your media to be copied to once the download has completed. You can leave this as default as long as you do not have anything else running on the same port. This will be the port that you will be accessing the web interface of Sonarr on. The important options to look at here are Host Port 1. This will be discussed in an up and coming blog post for reverse proxies. This is so I can use the Linuxserver.io Letsencrypt container with their proxy configs to automatically set up the reverse proxy. You can see from my screenshot that I am using a custom network called proxynetwork. You will now see the page for setting up the container settings. We will be using the Linuxserver.io containers as I have always had a positive experience with them. You should see a few different versions popping up from different providors. You will need to browse to the APPS tab on your Unraid server and search for Sonarr. Once you have the shares set up you can now finally get round to installing Sonarr. You will also need your download folder share setting up but this should be done when setting up the downloader. Everything is else is pretty much standard settings. I have chosen to Automatically split only the top two directory levels as this should keep all season folders on the same drive. I have chosen to have individual shares for my media.īelow is a screen shot of my current settings for my TV show share. The usual setup for Sonarr would be to have a Media share that contains a TV subfolder. These will be accessable from your network so other applications can access them. Shares are where Sonarr will be accessing your downloads and putting the TV shows on your Unraid server. You can find a guide on how to do that HERE Shares # You need to install the Community Applications plugin. Community Applications Plugin #įirst thing first. Once you have the Community Applications plugin installed you are just a few clicks away from automating your TV show consumption. The “sonarr” container isn’t “broken” as it does work perfectly for the 5 minutes it actually remains running.Installing Sonarr couldn’t be any easier when installing using Docker on and Unraid server. It ran as “sonarr2” for nearly a week (before I stopped it myself). I repeated this name change several times with the same result - “sonarr” always stops after ~5 minutes, “sonarr2” never stopped. I changed it to “sonarr2” again and it ran for several hours again. I then stopped the container, deleted the old “sonarr” container and renamed the new one to “sonarr”. I recreated an identical copy of the container with a different name - “sonarr2” - and it ran for several hours. My container was called “sonarr” when the problem first occurred. ![]() It seems to be the name of the container causing the issue, not what is in it. ![]() I don’t think that the issue is actually with sonarr itself though. I had a sonarr docker container which was working fine for months (if not years), but then suddenly would only run for 5 minutes without stopping. I really hope someone can help me as this is very strange, and I have left everyone on the Unraid forum bewildered. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |