Where Does Unpackerr Store Its Config?
Unpackerr reads unpackerr.conf in TOML format. Docker mounts it at /config; Linux packages use /etc/unpackerr instead.
Last updated
Unpackerr configures through unpackerr.conf, a TOML file with sections per *arr app, watched folder, and hook. Docker setups mount a host folder at /config and place the file at /config/unpackerr.conf; the container writes a default there on first start when none exists. Package installs on Linux use /etc/unpackerr/unpackerr.conf with a systemd service instead.
Set a log file early. Extraction failures without logs are guesswork, and the default has no log file configured. Point UN_LOG_FILE or the config value at your downloads mount so the log sits next to the files it describes. Permissions matter too: Unpackerr needs write access to every download path it extracts.
Where Unpackerr stores this, by platform
/config/unpackerr.conf (Docker)
TOML config with [[sonarr]], [[radarr]], [[folder]] blocks. The container writes defaults here on first start. Replace with generator output and restart. Mount the parent folder, not the file alone, for clean rewrites.
/etc/unpackerr/unpackerr.conf
Same TOML layout via the Linux package repo. Edit with sudo and restart the unpackerr service. macOS Homebrew uses /usr/local/etc/unpackerr/unpackerr.conf by analogy.
Frequently asked questions
how do i create an unpackerr config file
Use the web generator at notifiarr.com/unpackerr, fill in your *arr URLs and keys, and paste the result over unpackerr.conf. Restart the container. At minimum uncomment one [[header]] block with its url and api_key.
environment variables or config file for unpackerr
Both work together, and variables win. Compose users often skip the file entirely and set UN_SONARR_0_URL style variables. File users mount /config/unpackerr.conf. Mixing is fine; check env first when a file value seems ignored.
Notice an outdated path? Let us know.