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.
#SONARR FIX PATH IS ALREADY CONFIGURED AS A ROOT FOLDER HOW TO#
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 This guide is more conceptual in nature while TRaSH's tutorial walks you through the process.
![sonarr fix path is already configured as a root folder sonarr fix path is already configured as a root folder](https://www.besttechtips.org/wp-content/uploads/2019/12/anytrans-driver3-800x400.png)
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.