Skip to content

Add Docker-aware image inventory and scoped cleanup - #61

Open
huntharo wants to merge 26 commits into
fix/artifact-classification-evidencefrom
feat/docker-inventory
Open

huntharo wants to merge 26 commits into
fix/artifact-classification-evidencefrom
feat/docker-inventory

Conversation

@huntharo

@huntharo huntharo commented Sep 27, 2026 •

Copy link
Copy Markdown
Owner

DiskHound had no Docker-aware inventory, so filesystem sizes could not explain images versus containers, volumes and build cache. Add an opt-in Docker tab with daemon-reported resource summaries, paginated image rows, logical/shared/unique sizes, container references, and explicit unknown acquisition provenance.

Image tags, digests and build metadata cannot reliably prove whether this machine pulled or built an image. The UI makes no such guess. Docker.raw and whole VM storage remain outside this feature and are never cleanup targets. Primary Docker documentation and implementation references are recorded in docs/docker-inventory.md.

Removal is limited to one full image ID, confirmed in a native dialog with the pinned endpoint and a warning about unreproducible local builds. Recheck references before image rm --no-prune; never force, prune broadly, start Docker, or remove volumes/containers/build cache. Docker conflicts propagate without destructive fallback. Remote/ambiguous endpoints are rejected before daemon calls. Requests are asynchronous, cancellable and bounded by 20 seconds and 8 MiB each. No automatic polling or application persistence writes are introduced.

Validation:

  • bun run typecheck
  • bun run test — 731 passed, 3 skipped after rebasing onto 735643d; includes 21 Docker tests for operation-count scaling at 1,000/8,000 images, endpoint/environment isolation, cancellation, CLI bounds, stale usage, confirmation and conflicts
  • bun run build:e2e — passes; existing renderer chunk-size warning
  • bunx playwright test e2e/docker.spec.ts e2e/file-categories.spec.ts — both pass after rebase; Docker IPC fixtures cannot contact a real daemon, screenshot visually checked
  • Read-only real CLI probe reported this machine's stopped daemon correctly; it was not started. No real Docker data was removed.

Limits: unknown provenance; only the first image tag is displayed; external buildx cache may be absent; aggregate sizes are daemon estimates from separate requests and do not promise host disk reclamation. CLI must be on PATH. No recurring SSD writes to budget.

Stacked on #56 (fix/artifact-classification-evidence), rebased onto 735643d. Parent VM/installer classification, renderer filters and cleanup exclusions are preserved. No filesystem classification changes in this PR.

@huntharo
huntharo force-pushed the feat/docker-inventory branch from a21bdf7 to 3c9843d Compare September 27, 2026 18:00
@huntharo
huntharo force-pushed the feat/docker-inventory branch from 3c9843d to 213deda Compare September 28, 2026 23:12
@huntharo
huntharo force-pushed the fix/artifact-classification-evidence branch from f2887a6 to 82eee4a Compare September 28, 2026 23:15
@huntharo
huntharo force-pushed the fix/artifact-classification-evidence branch from 5097c19 to 749a726 Compare October 16, 2026 12:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant