Docker image & resource cleanup helper, on a schedule!
A sleek, lightweight web interface to automatically clean up Docker resources on a schedule. Built with Python (Flask) · Docker SDK · APScheduler · Gunicorn
Keep your Docker host tidy with scheduled cleanup of unused images, containers, networks, and volumes.
- 🕐 Flexible scheduling - Daily, Weekly, or Monthly cleanup runs
- 🌍 Timezone aware - Configure your local timezone
- 🕒 12/24-hour time format - Choose your preferred time display
- 🧹 Selective cleanup - Choose what to prune: containers, images, networks, volumes
- 🔔 Smart notifications - Gotify or ntfy.sh support with optional change-only alerts
- 🎨 Modern UI - Dark theme with smooth animations and responsive design
- 🔒 Safe & controlled - Manual trigger option and detailed logging
- 📊 Detailed reports - See exactly what was cleaned and how much space was reclaimed
The overall look and feel of the PruneMate dashboard
Configure when and how often PruneMate should clean up your Docker resources.
Select which Docker resources to clean up and configure advanced options.
Set up notifications via Gotify or ntfy.sh to stay informed about cleanup results.
Get detailed statistics notifications about what was cleaned and how much space was reclaimed.
Gotify :
ntfy :
docker-compose.yaml:
services:
prunemate:
image: anoniemerd/prunemate:latest
ports:
- "7676:8080"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./logs:/var/log
- ./config:/config
environment:
- PRUNEMATE_TZ=Europe/Amsterdam # Change this to your desired timezone
- PRUNEMATE_TIME_24H=true #false for 12-Hour format (AM/PM)
restart: unless-stoppedVolume explanations:
/var/run/docker.sock- Required for Docker API access./logs- Stores application logs (rotating, 5MB max per file)./config- Stores configuration and state files
| Variable | Default | Description |
|---|---|---|
PRUNEMATE_TZ |
UTC |
Timezone for scheduling (e.g., Europe/Amsterdam, America/New_York) |
PRUNEMATE_TIME_24H |
true |
Time format: true for 24-hour, false for 12-hour (AM/PM) |
PRUNEMATE_CONFIG |
/config/config.json |
Path to configuration file |
Access the web interface at http://localhost:7676/ (or your server IP) to configure:
Schedule Settings:
- Frequency: Daily, Weekly, or Monthly
- Time: When to run the cleanup (supports both 12h and 24h format)
- Day: Day of week (for weekly) or day of month (for monthly)
Cleanup Options:
- ☑️ All unused containers
- ☑️ All unused images
- ☑️ All unused networks
- ☑️ All unused volumes
Notification Settings:
- Provider: Gotify or ntfy.sh
- URL: Your notification server URL
- Token/Topic: Authentication token (Gotify) or topic name (ntfy)
- Only notify on changes: Only send notifications when something was actually cleaned
- Scheduler runs every minute checking if it's time to execute
- Loads latest config from persistent storage
- Executes Docker prune commands for selected resource types
- Collects statistics on what was removed and space reclaimed
- Sends notification (if configured and enabled)
- Logs everything with timezone-aware timestamps
/config/
├── config.json # Your configuration (persistent)
├── prunemate.lock # Prevents concurrent runs
└── last_run_key # Tracks last successful run
/var/log/
└── prunemate.log # Application logs (rotating, 5MB max)
Gotify is a self-hosted notification service.
Setup steps:
- Install and run Gotify server
- Create a new application in Gotify
- Copy the application token
- Configure in PruneMate:
- Provider: Gotify
- URL:
https://your-gotify-server.com - Token: Your application token
ntfy.sh is a simple pub-sub notification service (self-hosted or public).
Setup steps:
- Choose a unique topic name (e.g.,
prunemate-alerts) - Configure in PruneMate:
- Provider: ntfy
- URL:
https://ntfy.sh(your self-hosted instance) - Topic: Your chosen topic name
Subscribe to notifications:
- Web: Visit
https://ntfy.sh/your-topic - Mobile: Install the ntfy app (Android / iOS) and subscribe to your topic
- Desktop: Use ntfy desktop app or web browser
| Problem | Solution |
|---|---|
| ❌ Can't access web interface | • Check if port 7676 is available and not blocked by firewall • Verify container is running: docker ps• Check logs: docker logs prunemate |
| ⚙️ Container not starting | • View startup errors: docker logs prunemate• Verify Docker socket is accessible • Check if port 7676 is already in use |
| 🔒 Permission denied errors | • Ensure /var/run/docker.sock exists and is accessible• On Linux, Docker daemon must be running • User running Docker must have proper permissions |
| 🕐 Wrong timezone in logs/schedule | • Set PRUNEMATE_TZ environment variable correctly• Restart container after changing: docker-compose restart• Verify timezone in logs matches expected |
| 📧 Notifications not working | • Test notification settings in web interface • Verify notification server URL is accessible • Check token/topic is correct • Review logs for error messages |
| 🗂️ Configuration not persisting | • Ensure ./config volume is mounted correctly• Check file permissions on host ./config directory• Verify container has write access |
| 🧹 Cleanup not running on schedule | • Check schedule configuration in web interface • Verify timezone is set correctly • Review logs: "Next scheduled run" messages • Ensure container is running continuously |
What the logs contain:
- ✅ Scheduler heartbeats (every minute)
- 📝 Configuration changes
- 🧹 Prune job executions with results
- 📨 Notification delivery status
- ❌ Error messages and warnings
- ✨ Added 12/24-hour time format support via
PRUNEMATE_TIME_24Henvironment variable - 🌍 Improved timezone handling across all components (logs, scheduling, notifications)
- 🎨 Enhanced UI with custom time picker for 12-hour mode (hour 1-12, minutes, AM/PM selector)
- 🐛 Fixed config synchronization issues in multi-worker setup
- ⚡ Simplified architecture: reduced from 2 workers to 1 for better reliability
- 📝 Implemented silent config loading to reduce log noise
- 🔧 Improved input validation with instant clamping and 2-digit limits
- 🔒 Added thread-safe configuration saving with file locking
- 🐛 Fixed scheduler not triggering at configured times
- 🔄 Config now reloads before each scheduled check to ensure synchronization
- 🔒 Added thread-safe config saving mechanism
- 📊 Improved logging with timezone-aware timestamps
- 🔔 Added notification support (Gotify & ntfy.sh)
- 🎨 Complete UI redesign with modern dark theme
- 📊 Enhanced statistics and detailed cleanup reporting
- 🎯 Added "only notify on changes" option
- 🔘 Improved button animations and hover effects
- 🎉 Initial release
- 🕐 Daily, Weekly, and Monthly scheduling
- 🧹 Selective cleanup options (containers, images, networks, volumes)
- 🌐 Web interface for configuration
- 📁 Persistent configuration and logging
Have questions or need help?
- 🐛 Bug reports: Open an issue on GitHub
- 💡 Feature requests: Open an issue on GitHub
- 💬 Questions & Discussion: Start a discussion on GitHub
- ⭐ Like PruneMate? Give it a star!
Author: Anoniemerd
🐙 GitHub: https://github.com/anoniemerd
📦 Repository: https://github.com/anoniemerd/PruneMate
License: MIT License
© 2025 – PruneMate Project
Keep your Docker host clean with PruneMate! 🐳🧹