Self-host Maintainerr with Levelrail
Rule-based media library cleanup for Plex and Jellyfin that works with Sonarr, Radarr and Seerr. MIT licensed. On first open, add your media server and arr apps in settings, then build rules.
- AuthorMaintainerr
- LicenceMIT
- Memory384 MiB
- Archarm64
- Services1
How to self-host Maintainerr
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/maintainerr/maintainerr:3.31.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 6246.
-
Fill in the secrets
1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Maintainerr requirements
- Memory
- About 384 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 6246
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Maintainerr. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Maintainerr docs page.
Deploy Maintainerr your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Maintainerr from the CLI
levelrail-cli templates install maintainerr --name my-maintainerr Deploy Maintainerr with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/maintainerr/install \
-d '{
"name": "my-maintainerr"
}' Maintainerr configuration
Maintainerr services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| maintainerr | ghcr.io/maintainerr/maintainerr:3.31.0 | 6246 | data -> /opt/data |
Maintainerr environment variables
| Variable | Service | Value |
|---|---|---|
| TZ | maintainerr | Preset by the template |
Ports and volumes
- Ports
- 6246
- Volumes
- 1 named mount: data -> /opt/data
Maintainerr FAQ
How much memory does Maintainerr need?
The catalog lists about 384 MiB of memory for Maintainerr.
Does Maintainerr run on arm64?
For Maintainerr, an arm64 image is published; amd64 is image published.
What licence is Maintainerr under?
Maintainerr is licensed under MIT, which is permissive, with few conditions on reuse.
Does Maintainerr need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Maintainerr use?
Maintainerr listens on port 6246 inside the stack.
Where does Maintainerr keep its data?
In a named volume: data mounted at /opt/data.
Can I deploy Maintainerr on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Maintainerr, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image ghcr.io/maintainerr/maintainerr:3.31.0 is what you deploy there.