Comment on Could somebody share a working Arr stack in docker with me?

• tyler@programming.dev ⁨1⁩ ⁨week⁩ ago

  Ah ok this is the comment that needs to be in the main post. First things first:

  You aren’t ‘installing’ radarr, sonarr, etc into any directories. They are containers, essentially entire operating systems located in a hidden folder on your server. You don’t ever touch these things directly, you only use docker commands to interface with them. There’s two ways to do that. Either directly running docker (docker run linuxserver:radarr -p blah blah blah) or with a docker compose (docker compose up). The docker compose way is the ‘easy’ way to do it (actually the easiest is just using unraid and clicking install, but we’ll ignore that since so many people are telling you a billion ways to do things). Docker compose means you can specify all of your applications in a single file, and how they interact with each other. You will run one command to start all of them at once. And then they will read from whatever folders you configure in the service. This might be a bit confusing because up above you might see other people’s docker compose files and they specify things like this:

    sonarr:
      container_name: sonarr
      network_mode: "service:gluetun"
      image: ghcr.io/hotio/sonarr:latest
      volumes:
        - /mnt/drive/volumes/sonarr/config:/config
        - /mnt/nas/TV:/mnt/TV
        - /mnt/nas/Downloads:/downloads
        - /etc/localtime:/etc/localtime:ro
      depends_on:
        - gluetun
      restart: 'unless-stopped'
  

  and you would think that they’re configuring the sonarr locations for their tv and downloads, etc. But that is not what is happening. They are simply mapping a local path /mnt/nas/TV to a path inside of the sonarr operating system /mnt/TV. This means that in Sonarr, in the web interface, you would configure the path /mnt/TV, NOT the path /mnt/nas/TV. You still have to configure EVERYTHING in the services themselves. All that docker is doing is setting up the operating system. Think of it like this, on a regular computer you can map network drives to letters like A, B, C, etc right? Well that’s exactly what you’re doing in docker, mapping ‘network’ (actually your main operating system) folders, to folders in the remote operating system (the one running in docker).

  In regards to having radarr rename things, you can have it do that, but you have to get the directory structure set up first, and you can run scripts to have nzbget or sabnzbd move things around for you. The experts on discord would be a much better help than most of us here I think, since they are all the devs on the project.

  original

  • Postmortal_Pop@lemmy.world ⁨1⁩ ⁨week⁩ ago

    I actually do get all of this, I guess my issue here is not know the venacular to explain it?

    I have the docker set up almost identical to that. I have an environment section with my user and group in it. My volumes are /home/user/docker/arr/radarr/config: /config /mnt/media1/1)unsorted: /downloads /mnt/media1/2)sorted: /movies. Inside radarr, add directory, /downloads shows the ~800 mkv files. When I go to import the movies in /download, it tells me there are no movies to import.

    I fixed this by looping mkdir to put every file in /mnt/media1/1)unsorted into its own folder. Now Radarr sees all of them and imports them.

    This hasn’t fixed literally every other facet of using them, I haven’t even set up sonarr yet. I’m still haven’t figured out gluten at all. Planning to run the yams thing someone else posted so I’ll see if that gets me anywhere.

    original