Repository navigation
Conversation
huntharo
force-pushed
the
feat/docker-inventory
branch
from
September 27, 2026 18:00
a21bdf7 to
3c9843d
Compare
huntharo
force-pushed
the
feat/docker-inventory
branch
from
September 28, 2026 23:12
3c9843d to
213deda
Compare
huntharo
force-pushed
the
fix/artifact-classification-evidence
branch
from
September 28, 2026 23:15
f2887a6 to
82eee4a
Compare
huntharo
force-pushed
the
fix/artifact-classification-evidence
branch
from
October 16, 2026 12:45
5097c19 to
749a726
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 typecheckbun 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 conflictsbun run build:e2e— passes; existing renderer chunk-size warningbunx 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 checkedLimits: 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.