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:
- Blog - all the things you can do with our containers including How-To guides, opinions and much more!
- Discord - realtime support / chat with the community and the team.
- Discourse - post on our community forum.
- Fleet - an online web interface which displays all of our maintained images.
- GitHub - view the source for all of our repositories.
- Open Collective - please consider helping us by either donating or contributing to our budget
Sonarr (formerly NZBdrone) is a PVR for usenet and bittorrent users. It can monitor multiple RSS feeds for new episodes of your favorite shows and will grab, sort and rename them. It can also be configured to automatically upgrade the quality of files already downloaded when a better quality format becomes available.
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/sonarr:latest
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:
Architecture | Available | Tag |
---|---|---|
x86-64 | ✅ | amd64-<version tag> |
arm64 | ✅ | arm64v8-<version tag> |
armhf | ❌ |
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
Tag | Available | Description |
---|---|---|
latest | ✅ | Stable releases from Sonarr (currently v3) |
develop | ✅ | Development releases from Sonarr (currently v4) |
Access the webui at <your-ip>:8989
, for more information check out Sonarr.
We have set /tv
and /downloads
as optional paths, this is because it is the easiest way to get started. While easy to use, it has some drawbacks. Mainly losing the ability to hardlink (TL;DR a way for a file to exist in multiple places on the same file system while only consuming one file worth of space), or atomic move (TL;DR instant file moves, rather than copy+delete) files while processing content.
Use the optional paths if you dont understand, or dont want hardlinks/atomic moves.
The folks over at servarr.com wrote a good write-up on how to get started with this.
Here are some example snippets to help you get started creating a container.
docker-compose (recommended, click here for more info)
---
version: "2.1"
services:
sonarr:
image: lscr.io/linuxserver/sonarr:latest
container_name: sonarr
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/London
volumes:
- /path/to/data:/config
- /path/to/tvseries:/tv #optional
- /path/to/downloadclient-downloads:/downloads #optional
ports:
- 8989:8989
restart: unless-stopped
docker cli (click here for more info)
docker run -d \
--name=sonarr \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Europe/London \
-p 8989:8989 \
-v /path/to/data:/config \
-v /path/to/tvseries:/tv `#optional` \
-v /path/to/downloadclient-downloads:/downloads `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/sonarr:latest
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.
Parameter | Function |
---|---|
-p 8989 |
The port for the Sonarr webinterface |
-e PUID=1000 |
for UserID - see below for explanation |
-e PGID=1000 |
for GroupID - see below for explanation |
-e TZ=Europe/London |
Specify a timezone to use EG Europe/London, this is required for Sonarr |
-v /config |
Database and sonarr configs |
-v /tv |
Location of TV library on disk (See note in Application setup) |
-v /downloads |
Location of download managers output directory (See note in Application setup) |
You can set any environment variable from a file by using a special prepend FILE__
.
As an example:
-e FILE__PASSWORD=/run/secrets/mysecretpassword
Will set the environment variable PASSWORD
based on the contents of the /run/secrets/mysecretpassword
file.
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022
setting.
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.
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)
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
- Shell access whilst the container is running:
docker exec -it sonarr /bin/bash
- To monitor the logs of the container in realtime:
docker logs -f sonarr
- container version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' sonarr
- image version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/sonarr:latest
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:
- Update all images:
docker-compose pull
- or update a single image:
docker-compose pull sonarr
- or update a single image:
- Let compose update all containers as necessary:
docker-compose up -d
- or update a single container:
docker-compose up -d sonarr
- or update a single container:
- You can also remove the old dangling images:
docker image prune
- Update the image:
docker pull lscr.io/linuxserver/sonarr:latest
- Stop the running container:
docker stop sonarr
- Delete the container:
docker rm sonarr
- Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your
/config
folder and settings will be preserved) - You can also remove the old dangling images:
docker image prune
-
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 sonarr
-
You can also remove the old dangling images:
docker image prune
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.
- We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
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-sonarr.git
cd docker-sonarr
docker build \
--no-cache \
--pull \
-t lscr.io/linuxserver/sonarr: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
.
- 24.11.22: - Bump develop branch to v4, rebase to Alpine 3.16.
- 03.08.22: - Deprecate armhf.
- 02.08.22: - Add armhf deprecation warning.
- 28.04.22: - Rebase master branch to mono 6.12 base (focal).
- 20.02.22: - Rebase develop branch to Alpine, deprecate develop-alpine branch.
- 28.12.21: - Add develop-alpine branch.
- 11.05.21: - Make the paths clearer to the user.
- 10.03.21: - Upgrade to Sonarr v3. Existing users are highly recommended to make a backup prior to update.
- 18.01.21: - Deprecate
UMASK_SET
in favor of UMASK in baseimage, see above for more information. - 05.04.20: - Move app to /app.
- 01.08.19: - Rebase to Linuxserver LTS mono version.
- 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.
- 01.02.19: - Multi arch images and pipeline build logic
- 15.12.17: - Fix continuation lines.
- 12.07.17: - Add inspect commands to README, move to jenkins build and push.
- 17.04.17: - Switch to using inhouse mono baseimage, adds python also.
- 14.04.17: - Change to mount /etc/localtime in README, thanks cbgj.
- 13.04.17: - Switch to official mono repository.
- 30.09.16: - Fix umask
- 23.09.16: - Add cd to /opt fixes redirects with althub (issue #25), make XDG config environment variable
- 15.09.16: - Add libcurl3 package.
- 09.09.16: - Add layer badges to README.
- 27.08.16: - Add badges to README.
- 20.07.16: - Rebase to xenial.
- 31.08.15: - Cleanup, changed sources to fetch binarys from. also a new baseimage.