Docker workspace
Containers, images, volumes and networks in the app, grouped by Compose project, each page opening with what is live, what it costs on disk and what can be reclaimed.
Why it matters
Answering "what is actually running, and where did the disk go" takes three commands and three tables that disagree about what size means — and then you delete things one at a time anyway. The workspace puts the four numbers that matter at the top of each page, names the project or the volume responsible, and lets you act on a selection instead of a single row.
What changes
Without it
- `docker ps`, then `docker ps -a`, then `docker system df`, then reconcile them by eye.
- A count of unused volumes, with no idea which ones they are.
- One `docker rm` per resource, or a prune command that takes more than you meant.
With 1VMTool
- Each page opens with running versus stopped, disk, and the reclaimable share.
- A meter per Compose project shows which stacks are still up, and the unattached volumes are named.
- Select the rows you filtered to and delete them in one confirmed pass.
How it works
Pick the engine, then the page
The Connection picker switches between every Docker context on the Mac, managed or not, and the sections — Docker Engine, Containers, Images, Volumes, Networks — belong to whichever one is selected.
Read the overview first
Containers lead with Running of total, Stopped, Compose projects and the writable layer with its reclaimable share; Images and Volumes lead with disk, in-use and reclaimable. Figures come from `docker system df` when the engine reports it, and a tile that cannot know says so instead of showing zero.
Find the one responsible
The Workload card breaks containers down per Compose project as running-over-total; Largest images ranks by size and shows the build cache separately; Volumes names the first five that nothing has mounted.
Work the list
Search by name, image, project or status, hide stopped containers with Running only, then Select All, and Delete Selected… confirms with exactly what will be removed — Docker's own refusals for running or referenced resources still apply.
What it covers
- Containers grouped by Compose project, with Standalone for the rest
- Usage overview on Containers, Images and Volumes, from `docker system df`
- Per-project running-over-total meters and a published-port count
- Largest images ranked, with build cache reported separately
- Unattached volumes named rather than counted
- Multi-select with bulk delete across containers, images, volumes and networks
- Container logs, live stats and a Terminal action per container
- Compose Up, Run Container, and image build, pull, load and transfer
- Refreshes every five seconds, and one failed listing never disconnects the rest
What you get out of it
- The disk answer without three command-line tables to reconcile
- Delete the set you actually meant, in one confirmed pass
- Containers and machines in one window, on one memory budget
Try it on your own Mac
Every screen states its limits before you commit to anything.