Where Does Janitorr Store Its Config?
Janitorr reads application.yml mounted at /config and writes logs to /logs. Both mounts are plain host folders you control.
Last updated
Janitorr configures through one YAML file. You mount application.yml into the container at /config/application.yml, alongside a /logs folder for file logging and a /data mount pointing at the media to clean. Logs also stream to stdout, but file logging keeps deletion history after the container is gone.
The file holds everything: *arr connections, the janitorr_keep exclusion tag, age thresholds, and scheduling. Since deletion age comes from *arr grab history rather than local state, the YAML plus logs fully describe the setup. Review the logs before widening any rule. Deletions follow config, and config mistakes delete real media.
Where Janitorr stores this, by platform
/config/application.yml (Docker mount)
application.yml with *arr connections, exclusion tags, and age rules. Mount the single file (not just the folder) so edits on the host apply inside. /logs and /data mount beside it.
Frequently asked questions
how do i migrate janitorr to a new server
Copy application.yml and the logs folder to the new host and mount them at the same container paths. Janitorr itself is stateless: queue state lives in the *arr apps, so the config file is the real backup.
can i install janitorr without docker
It runs only as a container image (or a manual build from source). There is no bare metal installer. Mount application.yml from the host and a /logs folder, and point it at your media with a /data mount.
Notice an outdated path? Let us know.