Radarr

Radarr is a movie collection manager for Usenet and BitTorrent users. It can monitor multiple RSS feeds for new movies and will interface with clients and indexers to grab, sort, and rename them. It can also be configured to automatically upgrade the quality of existing files in the library when a better quality format becomes available. Note that only one type of a given movie is supported. If you want both an 4k version and 1080p version of a given movie you will need multiple instances.

Installation

The Radarr team does not offer an official Docker image. However, a number of third parties have created and maintain their own. These instructions provide generic guidance that should apply to any Radarr Docker image. 

I use a docker image from linuxserver.io to install Radarr.  

If you prefer to install Radarr via another method go to Radarr's official downloads page.

Running Radarr as a container

Basic examples for getting this image running as a container

Docker Compose

---
version: "2"
services:
  radarr:
    image: linuxserver/radarr:4.3.2
    container_name: radarr
    restart: unless-stopped
    environment:
      - UMASK_SET=022 # control permissions of files and directories created by Radarr
      - TZ=Europe/London # Specify a timezone to use EG Europe/London, this is required for Radarr
      - PUID=1000 # for UserID
      - PGID=1000 # for GroupID
    volumes:
      - /host/path/to/movies:/movies # Location of Movie library on disk (See note in Application setup)
      - /host/path/to/downloads:/downloads # Location of download managers output directory (See note in Application setup)
      - /host/path/to/config:/config # Database and Radarr configs
    ports:
      - 7878:7878/tcp # The port for the Radarr webinterface

CLI

docker create \
  --name=radarr \
  -e UMASK_SET=022 `# control permissions of files and directories created by Radarr` \
  -e TZ=Europe/London `# Specify a timezone to use EG Europe/London, this is required for Radarr` \
  -e PUID=1000 `# for UserID` \
  -e PGID=1000 `# for GroupID` \
  -v /host/path/to/movies:/movies `# Location of Movie library on disk (See note in Application setup)` \
  -v /host/path/to/downloads:/downloads `# Location of download managers output directory (See note in Application setup)` \
  -v /host/path/to/config:/config `# Database and Radarr configs` \
  -p 7878:7878/tcp `# The port for the Radarr webinterface` \
  --restart unless-stopped \
  linuxserver/radarr:4.3.2

Avoid common pitfalls

Volumes and Paths

There are two common problems with Docker volumes: Paths that differ between the Radarr and download client container and paths that prevent fast moves and hard links.
The first is a problem because the download client will report a download's path as /torrents/My.Movie.2018/, but in the Radarr container that might be at /downloads/My.Movie.2018/. The second is a performance issue and causes problems for seeding torrents. Both problems can be solved with well planned, consistent paths.

Most Docker images suggest paths like /movies and /downloads. This causes slow moves and doesn't allow hard links because they are considered two different file systems inside the container. Some also recommend paths for the download client container that are different from the Radarr container, like /torrents.
The best solution is to use a single, common volume inside the containers, such as /data. Your Movies would be in /data/Movies, torrents in /data/downloads/torrents and/or usenet downloads in /data/downloads/usenet.

If this advice is not followed, you may have to configure a Remote Path Mapping in the Radarr web UI (Settings › Download Clients).

Ownership and Permissions

Permissions and ownership of files is one of the most common problems for Radarr users, both inside and outside Docker. Most images have environment variables that can be used to override the default user, group and umask, you should decide this before setting up all of your containers. The recommendation is to use a common group for all related containers so that each container can use the shared group permissions to read and write files on the mounted volumes.
Keep in mind that Radarr will need read and write to the download folders as well as the final folders.

Install Radarr

To install and use these Docker images, you'll need to keep the above in mind while following their documentation. There are many ways to manage Docker images and containers too, so installation and maintenance of them will depend on the route you choose.

• hotio/radarr:release

  hotio doesn't specify any default volumes, besides /config. Images are automatically updated multiple times in an hour if upstream changes are found. Hotio also builds our Pull Requests which may be useful for testing. Read the instructions on how to install the image.

• lscr.io/linuxserver/radarr:latest

  linuxserver.io is one of the most prolific and popular Docker image maintainers. They also maintain images for most of the popular download clients as well. LinuxServer specifies a couple of optional default volumes such as /movies and /downloads. The default volumes are not optimal nor recommended. Our recommendation is to use a single volume for the data, as mentioned above.