Automatically removes unused Docker Swarm objects like containers, volumes, and networks based on configurable age thresholds.
Docker GC is a garbage collection service designed for Docker Swarm environments that automatically cleans up unused Docker objects like containers, volumes, and networks. It helps prevent disk space exhaustion and maintains system hygiene by removing stale resources based on configurable age thresholds and intervals. The service can be deployed in Docker Swarm via docker-stack.yml or as a standalone Docker service using docker-compose.yml.
DevOps engineers and system administrators managing Docker Swarm clusters or Docker services who need automated cleanup of unused resources to optimize disk usage and maintain system performance. It is also suitable for teams running containerized applications in production environments where resource management is critical.
Developers choose Docker GC for its specialized integration with Docker Swarm, offering automatic cleanup tailored for orchestrated environments while maintaining flexibility through customizable policies like AGE and SLEEP parameters. Its unique STICKY_LABEL feature allows specific images to be protected from deletion, providing control over resource retention without manual intervention.
Garbage collector for Docker Swarm / Автоматическая сборка мусора для Docker и Docker Swarm
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Specifically designed for Docker Swarm, with deployment via docker-stack.yml as highlighted in the README, making it a tailored solution for orchestrated environments.
Allows setting AGE and SLEEP parameters in flexible Go duration formats (e.g., 10m, 1h30m), enabling precise control over when and how often unused objects are removed.
STICKY_LABEL functionality lets you exclude specific images from deletion by adding a simple label to the Dockerfile, as explained in the configuration section.
Can be deployed both in Docker Swarm using docker-stack.yml and as a standalone service via docker-compose.yml, offering versatility for different setups.
Does not automatically remove unused Docker images; it only targets containers, volumes, and networks, which limits comprehensive garbage collection without manual intervention.
Relies on SLEEP intervals for checks, meaning cleanup isn't triggered in real-time, potentially leading to delayed resource release in fast-changing environments.
Protecting images requires rebuilding them with LABEL directives and adjusting configurations, adding steps compared to simpler exclusion mechanisms.
English documentation is referenced to an external blog (Habr.com), which may be less reliable or up-to-date than official project docs, as noted in the README.