chore(docker): classify reclaimable RS2000 images, volumes, and CI task state #799

New issue

Closed

opened 2026-06-17 21:27:36 +02:00 by codex · 0 comments

codex commented

2026-06-17 21:27:36 +02:00

Collaborator

Summary

docker system df still reports large reclaimable areas after the safe RS2000 cleanup. This is not approval to prune. The platform needs a classification pass that separates rollback artifacts and persistent volumes from rebuildable cache and CI temp state.

Scope

Inventory reclaimable images, anonymous volumes, CI task volumes, and BuildKit cache classes.
Identify safe TTL/prefix policy candidates.
Preserve rollback images and persistent app volumes.
Produce a recommended prune policy with dry-run evidence before any deletion.

Spec sources (whitelist)

runbooks/rs2000-disk-hygiene.md
state/reports/rs2000-disk-hygiene-2026-06-17.md
state/reports/rs2000-runtime-health-closeout-2026-06-17.md

Do NOT read

Docker volume contents.
Application data directories.
Secret-bearing env files.
Full repo unless the whitelist points to a specific owner/source file.

Extracted context

Closeout docker system df:

Images          208       63        74.42GB   46.37GB (62%)
Containers      73        70        1.716GB   3.964kB (0%)
Local Volumes   92        35        57.52GB   16.6GB (28%)
Build Cache     621       0         70.98GB   59.37GB

Observed volume hotspots included BuildKit state volumes, model cache, Forgejo data, CI task volumes, and anonymous ~1G volumes. These need classification before deletion.

Acceptance criteria

Inventory lists top reclaimable images/volumes/caches with owner class and risk class.
CI/temp volume candidates have an explicit TTL or prefix rule.
Persistent app volumes and rollback images are marked non-prune by default.
Proposed cleanup command set is dry-run first and excludes docker volume prune as a blanket action.
A future live prune requires explicit approval if it deletes persistent data or rollback material.

Hard stops

No docker system prune --volumes.
No docker volume prune.
No image prune that removes the currently deployed rollback set.
No Buildx builder deletion without checking builder role and state.

Source

Created from RS2000 runtime health closeout on 2026-06-17.

## Summary `docker system df` still reports large reclaimable areas after the safe RS2000 cleanup. This is not approval to prune. The platform needs a classification pass that separates rollback artifacts and persistent volumes from rebuildable cache and CI temp state. ## Scope - Inventory reclaimable images, anonymous volumes, CI task volumes, and BuildKit cache classes. - Identify safe TTL/prefix policy candidates. - Preserve rollback images and persistent app volumes. - Produce a recommended prune policy with dry-run evidence before any deletion. ## Spec sources (whitelist) - `runbooks/rs2000-disk-hygiene.md` - `state/reports/rs2000-disk-hygiene-2026-06-17.md` - `state/reports/rs2000-runtime-health-closeout-2026-06-17.md` ## Do NOT read - Docker volume contents. - Application data directories. - Secret-bearing env files. - Full repo unless the whitelist points to a specific owner/source file. ## Extracted context Closeout `docker system df`: ```text Images 208 63 74.42GB 46.37GB (62%) Containers 73 70 1.716GB 3.964kB (0%) Local Volumes 92 35 57.52GB 16.6GB (28%) Build Cache 621 0 70.98GB 59.37GB ``` Observed volume hotspots included BuildKit state volumes, model cache, Forgejo data, CI task volumes, and anonymous ~1G volumes. These need classification before deletion. ## Acceptance criteria - Inventory lists top reclaimable images/volumes/caches with owner class and risk class. - CI/temp volume candidates have an explicit TTL or prefix rule. - Persistent app volumes and rollback images are marked non-prune by default. - Proposed cleanup command set is dry-run first and excludes `docker volume prune` as a blanket action. - A future live prune requires explicit approval if it deletes persistent data or rollback material. ## Hard stops - No `docker system prune --volumes`. - No `docker volume prune`. - No image prune that removes the currently deployed rollback set. - No Buildx builder deletion without checking builder role and state. ## Source Created from RS2000 runtime health closeout on 2026-06-17.

codex added the

labels

2026-06-17 21:27:36 +02:00