Docker Image Cleanup: Reduce Local and CI Storage Waste

Docker image cleanup on laptops and CI runners is not the same as registry retention. The waste is local disk pressure, slow runners, cache churn, and support tickets from developers whose machines fill up mid-build. The risk is deleting layers that make builds fast or removing images used by older projects that still need reproduction.

The useful output is a cleanup profile for each environment: what can be pruned automatically, what should be retained for active projects, and when CI cache eviction is cheaper than adding more disk. Keep developer workstations, shared runners, and release builders separate because their failure modes differ.

Key takeaways

• Treat each cleanup candidate as an owned system with dependencies, not anonymous clutter.
• Separate dangling layers, old branch images, builder cache, volumes, and release images before pruning.
• Prefer reversible changes first when deleting cache layers that speed up builds is still plausible.
• Leave behind a workstation and CI cleanup profile with retention windows, exclusions, and recovery steps.
• Measure the result as lower spend, lower risk, less operational drag, or clearer ownership.

Separate Disk Pressure From Build Cache

Start with one runner pool or workstation profile. Measure disk pressure, build-cache hit rates, active compose projects, and recovery expectations separately.

Field	Why it matters
Owner	Cleanup needs a person or team that can accept the decision
Current purpose	A short reason to keep the item, written in present tense
Last meaningful use	Image creation time, build cache hits, active compose projects, and CI job history
Dependency evidence	Dockerfiles, compose files, runner labels, release scripts, and project setup docs
Risk if wrong	The outage, data loss, access failure, or rollback gap the review must avoid
Next action	Keep, reduce, archive, disable, remove, or investigate

Do not make the inventory larger than the decision. A short list with owners and evidence beats a perfect spreadsheet that nobody is willing to act on.

Local Docker Evidence

The useful question is not “how old is it?” It is “what would break, become harder to recover, or lose accountability if this disappeared?” For Docker image cleanup, collect enough evidence to answer that without relying on naming conventions.

Check	What to look for	Cleanup signal
Dangling images	Untagged layers left by interrupted builds	Safe first candidates when no containers reference them
Builder cache	Cache size, last-used time, and expensive dependency layers	Prune by age only after measuring rebuild cost
Compose stacks	Local services and named volumes tied to active projects	Images can go; volumes may contain useful test data
CI runner role	Shared, project-specific, release, or ephemeral runner	Ephemeral runners can prune harder than release builders

Use several signals together. Activity can miss monthly jobs and incident-only paths. Ownership can be stale. Cost can distract from security or recovery risk. The strongest case combines runtime data, dependency checks, owner review, and a rollback plan.

If the evidence conflicts, label the item “investigate” with a named owner and review date. That is still progress because the next review starts with a narrower question.

Example Evidence Check

Use Docker’s disk-usage view to separate images, containers, volumes, and build cache before choosing a prune policy.

docker system df
docker system df -v
docker images --digests

The output shows where local disk is going and which images have stable digests. It does not prove that a volume, cache layer, or older project can be removed; use it to decide what deserves owner review.

Prune in the Right Place

Use the least permanent move that proves the decision. In Docker image cleanup, removal is only one possible outcome; reducing size, narrowing permission, shortening retention, archiving, or disabling a trigger may produce the same benefit with less risk.

• Start with dangling images and old branch tags on ephemeral runners.
• Keep expensive base layers for active repositories if rebuild time is the real cost.
• Never treat image pruning as volume cleanup; local volumes can contain fixtures or bug reproductions.

Track the cleanup candidate with a simple priority score:

Score	Good sign	Bad sign
Impact	Meaningful spend, risk, toil, noise, or confusion disappears	The item is cheap and low-risk but politically distracting
Confidence	Owner, purpose, and dependency path are understood	The team is guessing from age or name
Reversibility	Restore, recreate, re-enable, or rollback path exists	Deletion would be the first real test
Prevention	A rule can stop recurrence	The same pattern will return next month

Start with high-impact, high-confidence, reversible candidates. Defer confusing items only if they get an owner and a date; otherwise “defer” becomes another word for keeping waste permanently.

Local Cases That Need Patience

Some cleanup candidates are supposed to look quiet. Do not rush these cases:

• Release builders that need reproducible packaging environments.
• Developers supporting old branches, customer versions, or migration tests.
• CI caches where deleting layers increases queue time more than it saves storage.

For these cases, use a longer observation window, explicit owner approval, and a staged reduction. The point is not to avoid cleanup; it is to avoid making the first proof of dependency an outage.

Run the Cleanup Review

Run Docker image cleanup as a decision review, not an open-ended hygiene project.

1. Pick the narrow scope and export the candidate list.
2. Add owner, current purpose, last-use evidence, dependency checks, and risk if wrong.
3. Remove obvious false positives, then ask owners to choose keep, reduce, archive, disable, remove, or investigate.
4. Apply the least permanent useful change first.
5. Watch the signals that would reveal a bad decision.
6. Complete the final removal only after the review window closes.
7. Save the cleanup profile with prune targets, cache exclusions, and recovery notes.

For broader cleanup planning, use the cleanup library to pair this guide with related notes. If the cleanup has infrastructure impact, pair it with a visible owner, a rollback path, and a measurable business case. For infrastructure cleanup, the main cloud cost optimization checklist is a useful companion.

Prevent Local Image Bloat

Prevention should change the creation path, not just the cleanup path. For Docker image cleanup, the useful prevention fields are owner, reason to exist, removal trigger, and verification notes. Make those fields part of normal creation and review.

• Use ephemeral CI runners for noisy branch builds when possible.
• Publish a supported prune profile for workstations instead of relying on ad hoc advice.
• Pin base images and keep Dockerfiles lean so local caches do not multiply across similar builds.

The recurring review should be short: sort by impact, pick the unclear items, assign owners, and close the loop on anything nobody claims. If the review keeps producing the same class of candidate, fix the creation path instead of celebrating repeated cleanup.

Example Decision Record

Use a compact record so the cleanup can be reviewed later without reconstructing the whole investigation.

Field	Example entry for this cleanup
Candidate	Unused Docker images in developer machines and CI runners
Why it looked stale	Low recent activity, unclear owner, or no current consumer after the first review
Evidence checked	Owner trail, Runtime use, and owner confirmation
First reversible move	Prune dangling images on ephemeral runners before touching build cache
Watch signal	The metric, alert, job, route, query, or owner complaint that would show the cleanup was wrong
Final action	Keep, reduce, archive, disable, or remove after a window long enough to include scheduled and low-frequency use, not just a quiet afternoon
Prevention rule	Require owner and review-date metadata at creation time

This record is intentionally small. If the decision needs a long narrative, the candidate is probably not ready for removal yet. Keep investigating until the owner, evidence, reversible move, and prevention rule are clear.

FAQ

How often should teams do Docker image cleanup?

Use a window long enough to include scheduled and low-frequency use, not just a quiet afternoon for the first decision, then set a recurring cadence based on change rate. Fast-moving non-production systems may need monthly review; slower systems can be quarterly if every unclear item has an owner and a review date.

What is the safest first action?

The safest first action is usually ownership repair plus evidence collection. After that, add or repair ownership metadata before changing anything ambiguous. That creates a visible test before permanent deletion.

What should not be removed quickly?

Do not rush anything connected to rare scheduled work that runs monthly, quarterly, or only during incidents. Also slow down when the cleanup affects recovery, compliance, customer-specific behavior, rare schedules, or security response.

How do you make the decision useful later?

Write the decision as a small operational record: candidate, owner, evidence, chosen action, watch signals, rollback path, final date, and prevention rule. That format helps future engineers, search engines, and AI assistants understand the cleanup without guessing.