Controlarr
Controlarr is a free self-hosted Docker container scheduler that lets you stop, start, and restart containers on a simple 24-hour clock, with staged starts…
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
44/100 Fair
- Maintained
- 72last commit 17 days ago
- Popular
- 61 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 1
- Open issues
- 0
- Last commit
- 2026-11-04
- License
- MIT
- Activity
- rising
Checked 16 days ago - source: GitHub (p1zzm1ssile/Controlarr)
Resources & Compatibility
Requirements not published yet.
Checked 16 days ago - source: Docker Hub image tags and published docs
First-install notes
- Install on Unraid Open the Unraid Apps tab, search for Controlarr, and click Install. Mount the Docker socket so it can stop and start containers. source
- Install via Community Applications Open the Unraid Apps tab, search for Controlarr, and click Install. source
Fetched yesterday - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How do I schedule containers without using the web page?
Add controlarr.stop and controlarr.start labels to the target container with plain 24-hour times. Label-based schedules appear on the Controlarr page but can only be changed by editing the labels.
What does Controlarr need to access in order to stop and start containers?
It needs the Docker socket mounted into the Controlarr container. The quick-start example mounts /var/run/docker.sock to /var/run/docker.sock.
How should I preserve schedules made in the web page?
Schedules added on the page are saved to /config/schedules.yml. Mount /config to a host directory so those settings remain after updates or container rebuilds.
What security controls are available for the web page?
Anyone who can open the page can stop and start containers, so set CONTROLARR_WEB_PASSWORD if it may be reachable by others. Set CONTROLARR_WEB_PORT=0 to turn the page off.
Answers sourced from github.com
Community
No community discussions collected yet.