Reminder that many folks find TRaSH's Hardlink Tutorial helpful and easier to understand than this guide. This is easy to say, but not so easy to understand and explain. The idea is that you run each Docker container as its own user, with a shared group and consistent volumes so every container sees the same path layout. This article will not show you specifics about the best Docker setup, but it describes an overview that you can use to make your own setup the best that it can be. See this Docker Guide and TRaSH's Docker Tutorial instead for how to setup Docker Compose. Capabilities are hidden and some don't work at all on ARM platforms.Pulls every tag on update when you don't set a specific tag.Inconsistent compose implementations on different architectures.No automatically created custom networks for inter-container communication.Incorrect order of source and target of mounts.It's strongly suggested to use Docker compose and to not use Portainer.Portainer should only for viewing docker container logs / container status.Portainer gives a pretty GUI for managing containers, but that is all it is useful for.Portainer should be avoided for setting up docker containers It removes the hassle around user management and permissions on the host device and features some other applications like PleX. It is basically a ready-to-go collection of files and only requires you to run two things to get the entire thing online. Note: This is a GitHub repository aimed at beginners who want to use Docker for their Servarr stack. This guide is more conceptual in nature while TRaSH's tutorial walks you through the process. Note: Many folks find TRaSH's Hardlink Tutorial helpful and easier to understand than this guide. And most of all, ignore most of the Docker image’s path documentation! Using one volume (so the download folder and library folder are on the same file system) makes hardlinks and instant moves (atomic moves) possible for Sonarr, Radarr, Lidarr and Readarr. Consistent path definitions between all containers that maintains the folder structure. TL DR: An eponymous user per daemon and a shared group with a umask of 002. Running Docker containers with umask 000.Running Docker containers as root or changing users around.Correct outside paths, incorrect inside paths.Hopefully this helps and sorry if formatting is garbage. Add the same http (top right corner of unraid dashboard and the port is the same as the delugevpn 8118 or whatever.ĭo not type when adding the address in the proxy setting in radarr or sonarr it just needs the numbers I.E .xxx. From there load the web ui of sonarr/radarr and in the setting you will see the option for proxy. If you used jackett then its very straightforward and a simple google search for "how to set up jackett in unraid" should do the trick. Next you install Radarr/Sonnarr and add indexers however you chose. Its 8118 or something, not home cant remember off the top of my head. The port is the one in the delugevpn container that says for routing traffic. The http adress is the one in the top right corner of your unraid dashboard. In the settings there is a section for using a privoxy. Simply install jacket and load the web UI up when its done. Make sure you turn on the privoxy setting.įrom here you have the option to use Jackett as your source indexer. Follow spaceinvaders guide on setting it up. So ill share with you what i did and hopefully this helps. I looked for a good straight forward answer when i was doing this and there are so many ways to tackle the task.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |