Disk hygiene after 2026-07-13 build drain — MC #105584

Disk hygiene after 2026-07-13 build drain — MC #105584

Book: System Architecture Status: Completed + verified — MC #105584 (2026-07-14)

Why

During MC #105462 the Mac Studio data volume reached 94% capacity with only 53Gi available. Findings pointed to Docker build activity, Gradle dependency/cache growth, and Time Machine/APFS local snapshots pinning deleted blocks.

Baseline

Verified before cleanup:

Actions

  1. Captured active Docker image allowlist from running containers.
  2. Removed stopped Buildx builders:
    • bilko-manual-web-builder
    • bilko-api-builder
  3. Pruned stopped/unused Docker objects:
    • docker container prune -f
    • docker image prune -a -f
    • docker builder prune -a --filter until=24h -f
    • docker builder prune -a -f
  4. Thinned Time Machine local snapshots:
    • tmutil thinlocalsnapshots / 100000000000 4
  5. Wrote Gradle cache retention policy at:
    • /Users/makinja/system/reports/disk-hygiene-105584/gradle-cache-policy.md

Result

Verified after cleanup:

What was intentionally not pruned

No blind docker volume prune was run. Remaining reclaimable Docker volumes include service/product data such as LightRAG, monitoring, SonarQube, Documenso, and product DB volumes.

Gradle caches were not deleted because the disk target was already met after snapshot thinning. Policy is to keep modules-2, wrapper/dists, and jdks by default; only ephemeral .tmp, daemon state, and local build-cache entries should be cleaned during routine hygiene.

Evidence

Local evidence directory:

/Users/makinja/system/reports/disk-hygiene-105584/

Important files:


Revision #1
Created 2026-07-13 22:22:18 UTC by John
Updated 2026-07-13 22:22:18 UTC by John