Where Does Huntarr Store Its Data?
Huntarr keeps settings, its database, logs, and backups in a single /config volume. Map it persistently or every update wipes you.
Last updated
Huntarr puts all of its state in /config: connection settings for the *arr apps, the SQLite database, logs, NZB queue state, and automatic backups. The container exposes one port (usually 9705) and treats /media and /downloads as optional extras for library hunting features.
That single volume is the whole backup. Stop the container, copy the host folder behind /config, and you can rebuild anywhere by mounting it back at the same container path. Anonymous volumes technically persist but hide the files from you, so bind a real host path. Set PUID and PGID to match your media ownership and permission errors stay away.
Where Huntarr stores this, by platform
/config (Docker volume)
Settings, SQLite database, logs, NZB queue state, and backups. /media and /downloads mount separately and only matter for Movie, TV, and NZB hunt features.
Frequently asked questions
how do i back up huntarr
Copy the whole mapped /config folder (settings, database, logs, backups) with the container stopped. Restore by mounting it at /config on the new host. Enable automatic backups in Settings before major changes.
why is huntarr empty after every update
The /config mount is missing or anonymous. Only /config is required, but it must map to a real host path or named volume. Without it the database, history, and NZB queue state evaporate on every recreate.
Notice an outdated path? Let us know.