How to set up Radarr without Docker

Grabs the movies on your wishlist, automatically. Cresdock runs it on a server you own, from a catalogue, with no Docker and no reverse proxy to configure.

What Cresdock does for you with Radarr

Its configuration is written before the container ever starts — including the web address it lives at, so Radarr generates correct links from the first page load instead of half-working behind a prefix.
Reached through your panel login. There is no second password to invent for Radarr and no port to open on your firewall.
Your Downloads and Media folders are already mounted, and they are the SAME folders your other apps see — so files land where the rest of your setup expects them, with no path mapping to work out.
Seeded with its own API key and web address the moment it's installed — reachable at your panel address immediately, authenticated through your panel login.
If you also install Recyclarr, it wires itself to Radarr automatically for TRaSH-guide quality profiles.
Install a download client — qBittorrent, Deluge, Transmission or SABnzbd — and Radarr is introduced to it for you, in whichever order you install the two: new films are handed over to fetch, and filed away once they arrive. ruTorrent is the exception, and stays yours to add.
Search works the same way. Prowlarr keeps Radarr's list of sites up to date on its own, and Radarr searches through Jackett or NZBHydra2 if you run one of those instead. The site accounts themselves stay yours, because they're your accounts.
Telling Plex, Jellyfin or Emby that something new has landed is the step left to you: it needs a key made inside your media server after you've created your account there, so there is none to hand over beforehand.

Why run Radarr yourself

The whole point of these tools is that they run unattended. On a desktop that gets shut down, they simply miss things.

What kind of server Radarr needs

These are small, patient programs. They spend most of their time asleep and wake up to check for something new, so 1 GB of memory covers several of them at once. What they need is to be running when you aren't watching.

Cresdock itself is undemanding — it runs on a small rented server, an old desktop or a mini PC, on Ubuntu or Debian. Everything it installs shares that machine, so the honest question is not "will this app run" but "how much am I going to put on here in total".

Where to run Radarr

Radarr runs wherever Cresdock runs, and the choice is about the machine, not the app:

At home, on hardware you already own. A mini PC, an old desktop or a NAS that can run Debian. Cresdock works behind a home router with no port forwarding and no domain, so Radarr is reachable on your own network first and from outside only if you choose.
On a rented server. A small VPS is enough for most apps and is the usual answer when Radarr should be reachable from anywhere. The setup guide covers the specs and the one-command install.
Through a provider that runs Cresdock. Hosting companies deploy Cresdock workspaces for their customers, so Radarr can come with a server you rent rather than one you set up — ask your provider, or see how providers offer it.

Installing Radarr

Put Cresdock on a server
One line on any Ubuntu or Debian machine — a rented VPS, a spare PC, a home server. It sets itself up.
Pick Radarr from the catalogue
Click Install. The panel pulls the image, writes the configuration, gets a certificate and starts it.
Open it from your dashboard
Its address and any login details are on its card. Start, stop, update, roll back or remove it from the same place, any time.

What this replaces

Doing it by hand means writing something like this, then keeping it working:

services:
  radarr:
    image: lscr.io/linuxserver/radarr:5.28.0.10274-ls286
    restart: unless-stopped
    ports:
      - "7878:7878"
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - ./radarr/config:/config
      - ./downloads:/downloads
      - ./media:/media

And that is the easy half. Still to do:

Install a reverse proxy and write a server block for it
Get a TLS certificate and set up automatic renewal
Create the folders above with the right ownership, or it will not start
Repeat all of it for the next app, and again on every server rebuild

On Cresdock, Radarr is one click and none of the above exists.

Common questions

Do I need to know Docker to run Radarr?

No. Cresdock installs Radarr in one click from its catalogue: it pulls the image, writes the configuration, gets an HTTPS certificate and starts it. Radarr's configuration is written before it first starts, so it opens already set up.

What happens to my files when Radarr updates?

Cresdock changes Radarr's own configuration only. Your downloads and your media are never touched by an update, a rebuild or a reinstall — that is a rule the software enforces, not a promise in a document.

Can I run Radarr at home instead of on a VPS?

Yes. Cresdock runs on a mini PC, an old desktop or anything that boots Debian, behind a normal home router with no port forwarding, and Radarr is reachable on your own network first. A rented server is only needed when Radarr must be reachable from anywhere without a VPN.

Can I remove Radarr later?

Yes. Cresdock removes Radarr in one click, and asks whether to keep its configuration for a future reinstall. Nothing else you have installed is affected.

Looking for what Radarr itself can do? That lives in its own documentation — this page is only about running it.

Pairs well with: Recyclarr · Sonarr · Rclone · how Radarr connects to your other apps

Before you start: where to rent a server · what it needs to run · Cresdock vs QuickBox · the seedbox panel in full · sell workspaces to your customers