Radarr (Core Service)¶
Radarr is a movie manager that automates searching, grabbing, and organizing movies through indexers and download clients.
At a glance¶
Test the connections before adding more requests. The saved root folder must also be visible to your media server.
flowchart TD
A["Open the app from its service page"] --> B
B["Test indexers and download client"] --> C
C["Choose the movie root folder and profile"] --> D
D["Add one intended item and follow import"] --> E
E["Scan and play it in the media server"]
First start¶
- Select Radarr and its download workflow in DUMB onboarding. Reopen onboarding from Settings → Launch Onboarding if needed.
- Open the Radarr service card. On DUMB Config, use Start if stopped, then select Embedded UI. Complete the application's login setup if prompted.
- Open Settings → Download Clients and test the client DUMB created for your selected workflow. Under Settings → Indexers, test an indexer added directly or synced from Prowlarr. Both connections must work to find and acquire media.
- Review Settings → Media Management → Root Folders. Choose the curated movie library folder for your workflow and use that same folder in your media server. Review Settings → Profiles to choose the quality you want.
- Add one intended movie, select that root folder and quality profile, and choose what to monitor. Check Activity → Queue while it is acquired and imported; check Activity → History if it fails.
- Scan your media-server library and play the imported item. Finish this test before adding a large library or enabling broad automated searches.
Keep the default SQLite database unless you are planning the separate migration below. The Decypharr, InfiniDysk and AltMount guides explain their different library folders.
Service Relationships¶
| Classification | Role |
|---|---|
| Core Service | Movie automation |
| Depends On | None |
| Optional | Decypharr, InfiniDysk, AltMount, Prowlarr |
| Exposes UI | Yes (Web UI) |
Technical details: configuration reference
Configuration in dumb_config.json¶
{
"radarr": {
"instances": {
"Default": {
"enabled": false,
"core_service": "",
"use_neutarr": false,
"use_profilarr": false,
"postgres_enabled": false,
"postgres_main_db": "",
"postgres_log_db": "",
"process_name": "Radarr",
"repo_owner": "Radarr",
"repo_name": "Radarr",
"release_version_enabled": false,
"release_version": "latest",
"clear_on_update": false,
"exclude_dirs": [],
"platforms": [],
"suppress_logging": false,
"auto_update": false,
"auto_update_interval": 24,
"auto_update_start_time": "04:00",
"pinned_version": "",
"port": 7878,
"config_dir": "/radarr/default",
"config_file": "/radarr/default/config.xml",
"log_file": "/radarr/default/logs/radarr.txt",
"command": [],
"env": {}
}
}
}
}
Key configuration fields¶
core_service: Set todecypharr,infinidysk,altmount, or a list of workflow keys to enable DUMB integration.use_neutarr: Opt this instance into NeutArr automation.use_profilarr: Opt this instance into Profilarr linking.postgres_enabled: Opt this instance into DUMB-managed PostgreSQL config. SQLite is the default; set this totrueonly when you want Radarr to use PostgreSQL.postgres_main_db/postgres_log_db: Optional database-name overrides. When blank, DUMB usesradarr-mainandradarr-logfor the default instance, or unique instance-scoped names for additional instances.port: Web UI port (default7878).pinned_version: Optional version pin for Radarr updates.repo_owner/repo_name: GitHub repo used for releases or branch builds.release_version_enabled/release_version: Use GitHub releases (e.g.,latest,nightly,prerelease, or a tag).clear_on_update: Clear the install directory before updating.exclude_dirs: Directories to preserve when clearing.platforms: Build platforms (defaults to["dotnet"]when using branches).config_dir,config_file,log_file: Paths for config and logs.
PostgreSQL database mode¶
SQLite is the default and needs no separate setup. If you want to move an existing Radarr instance to PostgreSQL, use Database Migration on its service page. Run a rehearsal, review the validation results, then use guarded cutover. Read the migration guide and back up the instance before proceeding.
Geek details: how PostgreSQL settings and startup are generated
When postgres_enabled is true, DUMB:
- enables the bundled PostgreSQL service if needed;
- creates the Radarr main/log databases in
postgres.databases; - starts PostgreSQL before Radarr; and
- writes the required
PostgresUser,PostgresPassword,PostgresHost,PostgresPort,PostgresMainDb, andPostgresLogDbentries to Radarr'sconfig.xml.
During onboarding, enabling postgres_enabled for Radarr is enough; you do not need to separately select PostgreSQL as an optional service.
This does not migrate existing SQLite data
Setting postgres_enabled: true changes the database backend Radarr starts with. It does not copy radarr.db into PostgreSQL.
If you enable this on an existing SQLite-backed Radarr instance without doing a manual migration, Radarr can start against fresh PostgreSQL databases and appear empty or newly initialized.
For an existing instance, use the Database Migration tool on its service page. Run a rehearsal first, review its table-count validation, and only then start guarded cutover. See SQLite to PostgreSQL Migration.
Radarr's upstream documentation still classifies existing SQLite migration as unsupported. Back up Radarr's /data/radarr persistence and PostgreSQL's /data/postgres persistence (internal paths /radarr/... and /postgres_data) before proceeding, even when using DUMB's guarded workflow.
PostgreSQL is not a temporary toggle
There is no known supported migration path from PostgreSQL back to SQLite for Radarr. Treat postgres_enabled: true as a long-term database choice unless you are willing to recreate the Radarr instance from scratch.
DUMB preserves the pre-cutover SQLite database and can restore its configuration, but it does not copy later PostgreSQL changes back into SQLite.
Repo-based installs and updates¶
Radarr now supports the same repository-based controls as other DUMB services.
- GitHub releases: Set
release_version_enabled: truewith a validrepo_owner/repo_name. - Default updater: Leave
release_version_enabled: falseto use the standard Arr updater.
GitHub sources take priority when enabled and are not a fallback. pinned_version only applies to the traditional Arr updater.
Integration with DUMB¶
- For Decypharr integration, set
core_servicetodecypharrand follow the Decypharr guide. - For InfiniDysk integration, set
core_servicetoinfinidyskand follow the InfiniDysk guide. - For AltMount integration, set
core_servicetoaltmountand follow the AltMount guide. - For combined workflows, set
core_serviceto a list such as["decypharr", "infinidysk", "altmount"]. - Use Prowlarr to centrally manage indexers and sync them to Radarr.
- DUMB enables Arr folder permission updates and applies permissions to configured root folders during integration.
- See Core Service Routing for how
core_serviceaffects automation.
Accessing the UI¶
Open the service from DUMB's Embedded UI tab when available. The native URLs below require the corresponding Docker host port to be published; use the port saved in your running configuration.
- Navigate to:
http://<host>:7878