Logrotate
A Docker container that runs logrotate to automatically rotate, compress, and remove log files for a Vitess database deployment.
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- 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.
64/100 Good
- Maintained
- 74last commit 80 days ago
- Popular
- 641,556 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
- Security check
- 81no serious findings, CI, tests, OpenSSF Scorecard 6.1/10
Based on 4 of 5 factors.
- GitHub stars
- 1,556
- Open issues
- 66
- Last commit
- 2026-09-02
- Latest release
- 3.22.0
- License
- GPL-2.0
- Activity
- stale
Checked 16 days ago - source: GitHub (logrotate/logrotate)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Check the main config and include folder Before the first real run, review /etc/logrotate.conf and make sure it includes /etc/logrotate.d (the folder with extra rules for apps like nginx). Without the right config, logrotate may miss important logs or use defaults that do not fit your system. source
- Enable the scheduled timer Run `sudo systemctl enable logrotate.timer` and `sudo systemctl start logrotate.timer` so logrotate runs automatically on schedule. systemctl is the command that turns on scheduled tasks, and without this timer your logs may not rotate until you start it manually, which can fill up disk space. source
- Keep the state file safe Back up /var/lib/logrotate/status, the file that remembers when each log was last rotated and which backup number is next. If it is lost, logrotate can rotate the wrong files, skip backups, or create unexpected filenames after a reinstall or move. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How do I make logrotate run automatically on a schedule?
Enable and start the systemd timer with sudo systemctl enable logrotate.timer and sudo systemctl start logrotate.timer. Without the timer, logs may not rotate until you run logrotate manually.
Which logrotate file should I back up to avoid rotation problems after a move?
Back up /var/lib/logrotate/status, because it remembers when each log was last rotated and which backup number is next. If lost, logrotate can rotate wrong files, skip backups, or create unexpected filenames.
What should I check in the logrotate config before the first real run?
Review /etc/logrotate.conf and make sure it includes /etc/logrotate.d, which holds extra rules for apps. Without the right config, logrotate may miss important logs or use defaults that do not fit your system.
What Docker options are available for log rotation?
You can use an external logrotate container, but that may cause concurrent access issues, or install logrotate within each container if it is available. Another option is to use Docker logs with configured rotation instead of application logs.
Answers sourced from github.com, github.com, github.com, www.redditmedia.com
Community
- Promtail and Logrotate : r/selfhosted - Reddit (reddit)
- It's almost 2023 - How do you logrotate? Seriously. - Reddit (reddit)
Collected 48 days ago - public community threads