recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues 1 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

status(2pc): add probe-5 evidence — surgical prune reclaimed 2.34GB (dangling+old only), all tagged images kept, disk bounded without -af

Browse Source 
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
autonomic-bot
2026-05-29 09:44:57 +01:00
parent b9bbd253eb
commit f6af7edd97
2 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
machine-docs/JOURNAL-2pc.md
View File

@ -84,3 +84,15 @@ finished (22.5s CPU), `systemctl is-system-running` → `running`.
**Docs/decisions.** `docs/runbook.md` (new "Image cache & prune policy" + updated rate-limit note),
`docs/warm.md` (autoPrune→ci-docker-prune), `DECISIONS.md` (Phase-2pc entry), `cc-ci-plan/IDEAS.md`
(deferred registry cache + revisit trigger). Gate claimed.
## 2026-05-29 — Probe-5 evidence: surgical prune reclaims, keeps tagged/recent
Ran the exact active-path command the gated unit uses (`docker image prune -f --filter until=24h`
+ container/builder variants) on the host to demonstrate surgical reclaim (the daily timer only
reaches this under ≥80% disk, but the command's effect is the same):
- all images 23→17, dangling 10→**4** (the 4 remaining are <24h old — the `until=24h` age gate kept
them), **2.341 GB reclaimed**, disk 31%→27% (19G→17G used).
- ALL tagged/in-use images survived (keycloak:26.6.2, mariadb:12.2, nginx:1.30.0, redis:8.6.3, …) —
no `--all`, so nothing tagged or container-referenced was touched.
Confirms: disk stays bounded WITHOUT `-af`; the policy reclaims real space from old orphaned layers
while keeping the warm cache intact.

2
machine-docs/STATUS-2pc.md
View File

@ -39,6 +39,8 @@ ssh cc-ci 'docker images -q | wc -l' # EXPECT:
grep -nE "until=24h|--all|--volumes|prune" nix/modules/docker-prune.nix
grep -n "autoPrune" nix/modules/swarm.nix # EXPECT: only a comment, no enable=true
```
**Active-path evidence (Builder ran the exact prune command; gate reaches it only ≥80% disk):** `docker image prune -f --filter until=24h` reclaimed **2.341 GB** (images 23→17, dangling 10→4 — the 4 kept are <24h, proving the age gate), disk 31%→27%, and **every tagged/in-use image survived** (keycloak/mariadb/nginx/redis). Disk bounded without `-af`.
**EXPECTED:** old timer not-found; `ci-docker-prune.timer` enabled+active (daily); manual run below
80% prints the no-op line and removes nothing; module flags are `--filter until=24h` only (never
`--all`/`--volumes`); swarm.nix has no live autoPrune.