Where Does Unmanic Store Its Config?
Unmanic keeps settings, plugins, and its database in a /config volume. Libraries and the transcode cache mount separately.
Last updated
Unmanic splits its Docker mounts three ways. The /config volume holds settings, installed plugins, and the internal database. Your media stays outside in a /library mount, and transcode temp files go to a cache path (conventionally /tmp/unmanic). Only /config needs a persistent volume for settings to survive.
Backups therefore mean one folder. Copy the host directory behind /config and you have the whole configuration. The library and cache mounts are disposable by comparison: libraries are your media, and the cache is just in-flight work. Keep PUID and PGID consistent so the new host can read the copied files.
Where Unmanic stores this, by platform
/config (Docker volume)
Settings, plugins, and database. Generated plugin state lives under /config/.unmanic. Bind this to a host folder; /library (media) and /tmp/unmanic (cache) mount separately and need no backup.
Frequently asked questions
how do i migrate unmanic to a new server
Copy the whole mapped /config folder (settings, plugins, database) with the container stopped. Libraries stay where they are; only remount them at the same container paths on the new host.
where should the unmanic cache directory live
Put it on fast local storage, ideally an SSD or tmpfs. Unmanic writes heavy transcode temp files to /tmp/unmanic, and a slow network share there throttles every job.
Notice an outdated path? Let us know.