Skip to content
Sonarr 3 docker image.
Branch: master
Clone or download
Latest commit 88f4a11 May 20, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
root/etc tweak Mar 8, 2019
.drone.yml update Apr 20, 2019
.gitattributes initial commit Mar 6, 2019
Dockerfile 3.0.1.499 May 20, 2019
README.md update readme Apr 21, 2019
manifest.tmpl update ci Apr 19, 2019

README.md

Sonarr3

badge badge badge

Donations

NANO: xrb_1bxqm6nsm55s64rgf8f5k9m795hda535to6y15ik496goatakpupjfqzokfc
BTC: 39W6dcaG3uuF5mZTRL4h6Ghem74kUBHrmz
LTC: MMUFcGLiK6DnnHGFnN2MJLyTfANXw57bDY

Starting the container

Just the basics to get the container running:

docker run --rm --name sonarr3 -p 8989:8989 -v /tmp/sonarr3:/config -e TZ=Etc/UTC hotio/sonarr3
sonarr3:
  container_name: sonarr3
  image: hotio/sonarr3
  ports:
    - "8989:8989"
  volumes:
    - /tmp/sonarr3:/config
  environment:
    - TZ=Etc/UTC

The environment variables PUID, PGID, UMASK, VERSION and BACKUP are all optional, the values you see below are the default values.

By default the image comes with a stable version. You can however install a different version with the environment variable VERSION. The value image does nothing, but keep the included version, all the others install a different version when starting the container.

-e PUID=1000
-e PGID=1000
-e UMASK=022
-e VERSION=image
-e BACKUP=yes
environment:
  - PUID=1000
  - PGID=1000
  - UMASK=022
  - VERSION=image
  - BACKUP=yes

Possible values for VERSION:

VERSION=image
VERSION=stable
VERSION=unstable
VERSION=https://download.sonarr.tv/v3/phantom-develop/3.0.1.371/Sonarr.phantom-develop.3.0.1.371.linux.tar.gz
VERSION=file:///config/Sonarr.phantom-develop.3.0.1.371.linux.tar.gz

Backing up the configuration

By default on every docker container shutdown a backup is created from the configuration files. You can change this behaviour.

-e BACKUP=no
environment:
  - BACKUP=no

Using a rclone mount

Mounting a remote filesystem using rclone can be done with the environment variable RCLONE. Use docker exec -it --user hotio CONTAINERNAME rclone config to configure your remote when the container is running. Configuration files for rclone are stored in /config/.config/rclone.

-e RCLONE="remote1:path/to/files,/localmount1|remote2:path/to/files,/localmount2"
environment:
  - RCLONE=remote1:path/to/files,/localmount1|remote2:path/to/files,/localmount2

Using a rar2fs mount

Mounting a filesystem using rar2fs can be done with the environment variable RAR2FS. The new mount will be read-only. Using a rar2fs mount makes the use of an unrar script obsolete. You can mount a rar2fs mount on top of an rclone mount, rclone mounts are mounted first.

-e RAR2FS="/folder1-rar,/folder1-unrar|/folder2-rar,/folder2-unrar"
environment:
  - RAR2FS=/folder1-rar,/folder1-unrar|/folder2-rar,/folder2-unrar

Extra docker priviliges

In most cases you will need some or all of the following flags added to your command to get the required docker privileges when using a rclone or rar2fs mount.

--security-opt apparmor:unconfined --cap-add SYS_ADMIN --device /dev/fuse
security_opt:
  - apparmor:unconfined
cap_add:
  - SYS_ADMIN
devices:
  - /dev/fuse
You can’t perform that action at this time.