11notes/sonarr repository overview

⁠SONARR

run Sonarr rootless

⁠INTRODUCTION 📢

Sonarr⁠ (created by Sonarr⁠) 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.

⁠SYNOPSIS 📖

What can I do with this? This image will give you a rootless⁠ and lightweight Sonarr installation for your adventures on the high seas arrrr!

⁠ARR STACK IMAGES 🏴‍☠️

This image is part of the so called arr-stack (apps to pirate and manage media content). Here is the list of all it's companion apps for the best pirate experience:

• 11notes/configarr⁠ - as your TRaSH guide syncer for Sonarr and Radarr
• 11notes/plex⁠ - as your media server
• 11notes/prowlarr⁠ - to manage all your indexers
• 11notes/qbittorrent⁠ - as your torrent client
• 11notes/radarr⁠ - to manage your films
• 11notes/sabnzbd⁠ - as your usenet client

⁠UNIQUE VALUE PROPOSITION 💶

Why should I run this image and not the other image(s) that already exist? Good question! Because ...

• ... this image runs rootless⁠ as 1000:1000
• ... this image is auto updated to the latest version via CI/CD
• ... this image is built and compiled from source
• ... this image supports 32bit architecture
• ... this image has a health check
• ... this image runs read-only
• ... this image is automatically scanned for CVEs before and after publishing
• ... this image is created via a secure and pinned CI/CD process
• ... this image is very small

If you value security, simplicity and optimizations to the extreme, then this image might be for you.

⁠COMPARISON 🏁

Below you find a comparison between this image and the most used or original one.

Why is this image not distroless? I would have loved to create a distroless, single binary image, sadly the way that Sonarr is setup makes it really difficult to compile a static binary from source. Enabling AOT breaks almost 30% of used libraries because they are not setup to be statically linked (like Assembly.GetExecutingAssembly().Location). It’s also not fixable with a single PR. This is something the Sonarr team would need to do.

⁠VOLUMES 📁

• /sonarr/etc - Directory of all your settings and database

⁠COMPOSE ✂️

name: "arrs"

x-lockdown: &lockdown
  # prevents write access to the image itself
  read_only: true
  # prevents any process within the container to gain more privileges
  security_opt:
    - "no-new-privileges=true"

services:
  sonarr:
    image: "11notes/sonarr:4.0.20"
    <<: *lockdown
    environment:
      TZ: "Europe/Zurich"
    volumes:
      - "sonarr.etc:/sonarr/etc"
    tmpfs:
      # required for read-only image
      - "/tmp:uid=1000,gid=1000"
    ports:
      - "3000:8989/tcp"
    networks:
      frontend:
    restart: "always"

volumes:
  sonarr.etc:

networks:
  frontend:

To find out how you can change the default UID/GID of this container image, consult the RTFM⁠.

⁠DEFAULT SETTINGS 🗃️

⁠ENVIRONMENT 📝

⁠MAIN TAGS 🏷️

These are the main tags for the image. There is also a tag for each commit and its shorthand sha256 value.

• 4.0.20⁠
• 4.0.20-unraid⁠
• 4.0.20-nobody⁠

⁠There is no latest tag, what am I supposed to do about updates?

It is my opinion that the :latest tag is a bad habbit and should not be used at all. Many developers introduce breaking changes in new releases. This would messed up everything for people who use :latest. If you don’t want to change the tag to the latest semver⁠, simply use the short versions of semver⁠. Instead of using :4.0.20 you can use :4 or :4.0. Since on each new version these tags are updated to the latest version of the software, using them is identical to using :latest but at least fixed to a major or minor version. Which in theory should not introduce breaking changes.

If you still insist on having the bleeding edge release of this app, simply use the :rolling tag, but be warned! You will get the latest version of the app instantly, regardless of breaking changes or security issues or what so ever. You do this at your own risk!

⁠REGISTRIES ☁️

docker pull 11notes/sonarr:4.0.20
docker pull ghcr.io/11notes/sonarr:4.0.20
docker pull quay.io/11notes/sonarr:4.0.20

⁠UNRAID VERSION 🟠

This image supports unraid by default. Simply add -unraid to any tag and the image will run as 99:100 instead of 1000:1000.

⁠NOBODY VERSION 👻

This image supports nobody by default. Simply add -nobody to any tag and the image will run as 65534:65534 instead of 1000:1000.

⁠SOURCE 💾

• 11notes/sonarr⁠

⁠PARENT IMAGE 🏛️

• 11notes/alpine:stable⁠

⁠BUILT WITH 🧰

• sonarr⁠
• 11notes/util⁠

⁠GENERAL TIPS 📌

• Use a reverse proxy like Traefik, Nginx, HAproxy to terminate TLS and to protect your endpoints
• Use Let’s Encrypt DNS-01 challenge to obtain valid SSL certificates for your services

⁠ElevenNotes™️

This image is provided to you at your own risk. Always make backups before updating an image to a different version. Check the releases⁠ for breaking changes. If you have any problems with using this image simply raise an issue⁠, thanks. If you have a question or inputs please create a new discussion⁠ instead of an issue. You can find all my other repositories on github⁠.

created 17.09.2026, 06:08:24 (CET)