Where Does Maintainerr Store Its Data?
Maintainerr stores its database and settings in /opt/data inside the container. Mount a persistent volume there or lose everything.
Last updated
Maintainerr keeps everything in /opt/data: the application database, rule definitions, run history, and connection settings. The image carries no state of its own, so that path must be a mounted volume. Without the mount, every recreate starts with a blank ruleset.
Permissions cause most support threads. Maintainerr writes as the configured user (1000:1000 unless you set one), and files it creates on the host inherit that ownership. Set the user to match your host, chown the data directory once, and the access errors stop. Media libraries mount separately and only matter for leftover-folder cleanup.
Where Maintainerr stores this, by platform
/opt/data (Docker volume)
Database, rules, history, and settings. Bind to a host folder readable by UID:GID 1000:1000 (or your configured user). The container side is always /opt/data.
Frequently asked questions
how do i back up maintainerr
Stop the container and copy the whole mapped /opt/data folder. Restore by mounting it at /opt/data on the new host. Rules, history, and Plex tokens travel together, so copy everything rather than single files.
maintainerr cannot access the data directory. what fixes it
Almost always a permissions problem. The container runs as UID:GID 1000:1000 by default, and the host data directory must be writable by that user. Match the user instruction to your host ownership and check with a shell inside the container.
Notice an outdated path? Let us know.