Docker Registry Cleanup & Garbage Collection Automation

Automates cleanup of old Docker image tags, preserving the latest 10 per image, runs garbage collection via SSH, and sends email notifications for success or failure.

n8n
Docker Registry Cleanup & Garbage Collection Automation

This n8n workflow provides a robust solution for maintaining Docker registries by automatically identifying and removing outdated image tags. It starts by fetching the catalog of repositories, retrieves all tags for each image, sorts them by recency, and deletes all but the most recent 10 tags (always preserving 'latest'). Following deletions, it executes registry garbage collection through SSH and dispatches email notifications summarizing the operation, including any errors or excused deletions.

Key benefits include significant storage space savings, improved registry performance by reducing bloat, and enforcement of customizable retention policies without manual intervention. The automation minimizes human error, supports scheduled execution, and handles failures gracefully with detailed reporting, making it ideal for production environments.

Use cases span DevOps teams managing private registries in CI/CD pipelines, enterprises with high-volume image pushes, or any setup where disk space and organization are critical. Customize retention (e.g., slice(0,10)), trigger frequency, and email templates easily. Prerequisites include Docker v2 API credentials, SSH access for GC, and SMTP setup; test DELETE operations in staging first.

$22.99
Last updated August 29, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Built-in Apps workflows

More from Petra Ortega

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.