Sign inSign up

gh0str1pp3r/radarr

By gh0str1pp3r

Updated about 7 years ago

radarr modified for 5.12 mono due to bugs in later versions

Image
0

50K+

gh0str1pp3r/radarr repository overview

linuxserver.io

The LinuxServer.io team brings you another container release featuring :-

  • regular and timely application updates
  • easy user mappings (PGID, PUID)
  • custom base image with s6 overlay
  • weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
  • regular security updates

Find us at:

  • Discord - realtime support / chat with the community and the team.
  • IRC - on freenode at #linuxserver.io. Our primary support channel is Discord.
  • Blog - all the things you can do with our containers including How-To guides, opinions and much more!

linuxserver/radarr

Docker Pulls Docker Stars Build Status

Radarr - A fork of Sonarr to work with movies à la Couchpotato.

radarr

Supported Architectures

Our images support multiple architectures such as x86-64, arm64 and armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling linuxserver/radarr should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

ArchitectureTag
x86-64amd64-latest
arm64arm64v8-latest
armhfarm32v7-latest

Version Tags

This image provides various versions that are available via tags. latest tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.

TagDescription
latestStable Radarr releases
5.14Stable Radarr releases, but run on Mono 5.14
nightlyNightly Radarr releases
previewAlpha Radarr releases, unsupported and for development only

Usage

Here are some example snippets to help you get started creating a container.

docker
docker create \
  --name=radarr \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/London \
  -e UMASK_SET=022 `#optional` \
  -p 7878:7878 \
  -v <path to data>:/config \
  -v <path/to/movies>:/movies \
  -v <path/to/downloadclient-downloads>:/downloads \
  --restart unless-stopped \
  linuxserver/radarr
docker-compose

Compatible with docker-compose v2 schemas.

---
version: "2"
services:
  radarr:
    image: linuxserver/radarr
    container_name: radarr
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
      - UMASK_SET=022 #optional
    volumes:
      - <path to data>:/config
      - <path/to/movies>:/movies
      - <path/to/downloadclient-downloads>:/downloads
    ports:
      - 7878:7878
    restart: unless-stopped

Parameters

Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

ParameterFunction
-p 7878The port for the Radarr webinterface
-e PUID=1000for UserID - see below for explanation
-e PGID=1000for GroupID - see below for explanation
-e TZ=Europe/LondonSpecify a timezone to use EG Europe/London, this is required for Radarr
-e UMASK_SET=022control permissions of files and directories created by Radarr
-v /configDatabase and Radarr configs
-v /moviesLocation of Movie library on disk
-v /downloadsLocation of download managers output directory

User / Group Identifiers

When using volumes (-v flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id user as below:

  $ id username
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)

 

Application Setup

Access the webui at <your-ip>:7878, for more information check out Radarr.

Support Info

  • Shell access whilst the container is running: docker exec -it radarr /bin/bash
  • To monitor the logs of the container in realtime: docker logs -f radarr
  • container version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}' radarr
  • image version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/radarr

Updating Info

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

Via Docker Run/Create
  • Update the image: docker pull linuxserver/radarr
  • Stop the running container: docker stop radarr
  • Delete the container: docker rm radarr
  • Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
  • Start the new container: docker start radarr
  • You can also remove the old dangling images: docker image prune
Via Docker Compose
  • Update all images: docker-compose pull
    • or update a single image: docker-compose pull radarr
  • Let compose update all containers as necessary: docker-compose up -d
    • or update a single container: docker-compose up -d radarr
  • You can also remove the old dangling images: docker image prune
Via Watchtower auto-updater (especially useful if you don't remember the original parameters)
  • Pull the latest image at its tag and replace it with the same env variables in one run:
    docker run --rm \
    -v /var/run/docker.sock:/var/run/docker.sock \
    containrrr/watchtower \
    --run-once radarr
    

Note: We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.

  • You can also remove the old dangling images: docker image prune

Building locally

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone https://github.com/linuxserver/docker-radarr.git
cd docker-radarr
docker build \
  --no-cache \
  --pull \
  -t linuxserver/radarr:latest .

The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static

docker run --rm --privileged multiarch/qemu-user-static:register --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

Versions

  • 13.06.19: - Add env variable for setting umask.
  • 10.05.19: - Rebase to Bionic.
  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
  • 09.09.18: - Add pipeline build process.
  • 24.02.18: - Add nightly branch.
  • 06.02.18: - Radarr repo changed owner.
  • 15.12.17: - Fix continuation lines.
  • 17.04.17: - Switch to using inhouse mono baseimage, adds python also.
  • 13.04.17: - Switch to official mono repository.
  • 10.01.17: - Initial Release.

Tag summary

Content type

Image

Digest

Size

181 MB

Last updated

about 7 years ago

docker pull gh0str1pp3r/radarr