Skip to main content

Updating the Arr Stack

Updating the Arr Stack

DetThis ärguide sammacovers mönsterhow förto allaupdate containrarthe iservices stacken.running Härin ärthe helaarr-stack: proceduren.Prowlarr, Radarr, Sonarr (TV), Sonarr (Anime), qBittorrent, and Seerr. All services run as Docker containers via Docker Compose on the arr-server VM.

The same pattern applies to every container in the stack — pull the new image, then recreate the container. This is generally safe: pulling doesn't touch anything running, and recreating only replaces containers whose image actually changed.

StegStep förby stegstep

1. LoggaLog in påto the arr-servernserver

ssh -i ~/.ssh/pve01 kq@192.168.200.20

2. GåGo tillto compose-mappenthe compose directory (därwhere docker-compose.yml ligger)lives)


cd ~/home/kq/arr-stack

3. HämtaPull nyathe new images — dettathis äris ofarligtsafe, detit laddaronly baradownloads, ner,it rördoesn't intetouch dethe köranderunning containrarnacontainers


docker compose pull
sonarr-tv sonarr-anime

(VillTo duupdate uppdateraonly allt:specific utelämnaservices, namnenname →them:

docker compose pull radarr sonarr-tv
 hämtar för alla tjänster.)

4. ÅterskapaRecreate containrarnathe medcontainers denwith nyathe imagennew image — detthis äris härwhere denthe kortabrief nedtidendowntime skerhappens (~30usually sek)well under a minute per service). Docker återskaparonly bararecreates decontainers containrar varswhose image faktisktactually ändrats:changed:

docker compose up -d

Or for specific services only:

docker compose up -d radarr sonarr-tv
sonarr-anime

5. VerifieraVerify atteverything deis ärup uppeand ochon påthe nynew version

docker compose ps

EllerAll kollaservices versionenshould ishow web-UI:tUp. Give them 30–60 seconds to fully initialize before checking further.

Check the version in each service's web UI (Systemusually under Settings → Status)General or the bottom of the sidebar), elleror via API.logs:

6. (Valfritt) Städa bort gamla images så de inte samlas på disken

docker imagecompose prunelogs -f
--tail=50

DetUpdating dueverything behöverat minnasonce

To update all six services in one go:

cd ~/arr-stack
docker compose pull
docker compose up -d

Service-specific notes

KommandoService VadNotes detafter gör
Riskfritt?updating docker compose pullProwlarr LaddarFeeds nerindexers nyto imageRadarr ✅and Ja,both rörSonarr ingetinstances. körandeAfter updating, check Settings → Apps to confirm all three still show as synced. Radarr Check Settings → Indexers still shows all indexers active. Sonarr (TV) / Sonarr (Anime) Two independent instances — update and verify separately. Confirm episode/series detection still works. qBittorrent Active torrents and settings persist across updates (stored in the config volume). Verify downloads/seeding resume normally. Seerr Stateless request frontend. Verify it can still reach Radarr/Sonarr and that a test request goes through.

Rolling back

If an update causes problems, you can pin back to the previous image.

    Find the image ID/digest that was running before the update:

    docker image ls --digests | grep <service-name>

    (Do this before pulling if you think you might need to roll back — note the current digest first.)

    Stop the affected service:

    docker compose stop <service-name>

    Temporarily pin the image in docker-compose.yml to the old digest:

    radarr:
  image: lscr.io/linuxserver/radarr@sha256:<previous_digest>

    Recreate with the pinned image:

    docker compose up -d <service-name>
    Återskapar containern 🟡 Kort nedtid, config bevaras docker image prune -f Raderar oanvända images ✅ Ja (bara det inget använder)
      Config försvinner aldrig — den ligger i ./config/<tjänst> på värden (volym), inte i containern. :latest i

      Once confirmed stable, either leave it pinned or revert the compose betyderfile att pull alltid hämtar senaste LinuxServer-bygget. Du styr inte exakt version — vill du låsa en version byter manto :latest motand t.ex.re-test later.

      If config itself got corrupted by the update (not just the binary), restore the relevant folder from a backup of :4.0.19~/arr-stack/config/.

      i

      Backing up before updates

      Config for every service lives under docker-compose.yml~/arr-stack/config/<service>/. A quick manual backup before a risky update:

      tar -czf ~/arr-stack-backup-$(date +%Y%m%d-%H%M%S).tar.gz -C ~/arr-stack config/

      If something won't come back up

      1. Återställning:Check strularthe enlogs nyfor version,that körspecific service: 
        docker compose downlogs <tjänstservice-name>
        och
      pekaCheck tillbakadisk påspace en— äldrea taggfull idisk compose,is ellera common cause of failed startups: 
      df -h ~/arr-stack
      Check config folder permissions look sane: 
      ls -la ~/arr-stack/config/
      Try a plain restart before anything more drastic: 
      docker compose uprestart -d<service-name>
      igen

      Update frequency

        All images here track :latest, so there's no fixed release cadence to wait for — configenupdates ärjust intaktmean såwhatever duthe tapparmaintainers inget.shipped since your last pull. For routine point releases, it's fine to just update. For anything that looks like a major version bump in the release notes, skim the changelog first — Prowlarr/Radarr/Sonarr occasionally have schema or config-format changes worth knowing about ahead of time.

        TvåFurther viktiga varningarreading

          Aldrig "Install" i Sonarr/Radarr-web-UI:t — de är updateMechanism: docker, så uppdateringen ska komma via pull, inte inifrån appen. qBittorrent är specialfallet — uppdatera den inte slentrianmässigt:
          • DenLinuxServer.io harimage 193docs: aktiva seeds, och TorrentLeech kan banna vissa versioner.https://docs.linuxserver.io/
          • :latestRadarr kanreleases: dra in en betaversion eller en version TL inte gillar.https://github.com/Radarr/Radarr/releases
          • InnanSonarr dureleases: körhttps://github.com/Sonarr/Sonarr/releases
          upProwlarr -dreleases: påhttps://github.com/Prowlarr/Prowlarr/releases qBit:qBittorrent kollareleases: atthttps://github.com/qbittorrent/qBittorrent/releases denSeerr nyareleases: versionen är en stabil release och inte på TL:s ban-lista. Säkrast är att pinna qBit till en specifik, känt-bra version i compose (lscr.io/linuxserver/qbittorrent:5.x.x) istället för :latest.https://github.com/seerr-team/seerr/releases
          Back to top