DockerSpace
See what Docker takes up on disk, project by project — and delete only what is genuinely unused.
Launch price · −50%Final price €48
383 licences left at the launch price
Docker quietly accumulates tens of gigabytes in images, volumes and build cache. DockerSpace groups it by project, shows you what is in use and what is not, and gives you per-project cleanup instead of all-or-nothing.
// the problem
Docker will not tell you who owns what. You see 90 images and 40 volumes with no idea which belong to the project you are working on and which are left over from one you finished a year ago.
The alternative is prune, which draws no distinction — or deleting by hand, which requires remembering what created each thing.
How it works, step by step
Six steps, in the order they happen. Nothing is deleted before step 05.
docker ps -a, docker images -a, docker volume ls and docker system df -v locally — nothing leaves for any server.com.docker.compose.project label off every container, image and volume and buckets them by the project that created them.The app's screens
What each screen shows
- 01 / 04
Every project, with what is its own
- One card per Compose project: how many containers are running, plus its containers, images and volumes, with their sizes.
- Every image carries two badges: “built” or “base”, and “exclusive” or “shared”, naming the other projects that use it.
- “Delete entire project” removes only what belongs to this project alone. Base images and anything shared with another project stay.
- The Containers, Images and Volumes buttons clean one category at a time, again only what is exclusive to the project.
- 02 / 04
Every image, with its state
- The table shows every image with the project it belongs to and a state: used by a container, shared (“Shared — keep”), unused or dangling.
- An image counts as used when its real identifier matches a container, running or stopped. The name plays no part.
- A base image no container uses, like node:18 in the frame, is marked “not offered for bulk removal”: bulk deletion leaves it alone.
- “Remove Selected (Safe Only)” skips the images in use and tells you which ones were blocked.
- 03 / 04
Volumes, by who uses them
- Volumes in use are grouped by project, with its state (running or stopped) and the container that uses them.
- Volumes of stopped projects are listed first and are never offered for deletion.
- Orphans with a project label, “check before deleting”, are kept apart from anonymous ones, “safe to remove”.
- Beyond the groups in the frame, a volume can also be “disputed” or “unknown”. Both are held back from every cleanup.
- 04 / 04
The confirmation says what goes and what stays
- Before anything is deleted, the dialog names the containers, built images and volumes that will be removed.
- The “KEPT” section shows what stays: here postgres:16, the base image another project also uses.
- For volumes, the warning says the data is permanently deleted. Nothing is removed until you confirm.
- Teardown runs in order: containers first, then images, then volumes, with each step written to the status bar.
// under the hood
docker system prune has two settings: delete nothing, or delete everything Docker thinks is unused — including things you needed.
DockerSpace scans your local state and groups it by the Compose project that created it. For every resource it tells you whether it is active, shared between projects, a base image, or orphaned — and only then offers to delete it.
Images in use are matched by their real identifier rather than by name, so an image used by a stopped container is not lost. Per-project cleanup removes that project's own containers, images and volumes while keeping what is shared.
The last scan is kept on disk, so opening the app shows you the previous state immediately instead of making you wait.
What DockerSpace does
Groups containers, images, volumes and build cache by Compose project
Classifies every resource: active, shared, base image or orphaned
Per-project cleanup that keeps whatever other projects still use
Images in use are matched by their real identifier, not by name
Stopped containers count too, so their image is not deleted underneath them
The last scan is kept on disk — opening the app shows state immediately
Works with both Docker Desktop and Colima
Every resource is sorted before it gets deleted
// licence
The diagnosis is free, the clean-up needs a licence
Everything that answers "what is eating my disk" works without a licence, safety checks included. The licence unlocks deleting.
Free, no licence
- Scanning and listing images, volumes and the build cache, with their sizes
- Grouping by Compose project, and how much space can be reclaimed
- The safety checks: what is in use, what is blocked, and the confirmation text that names what would be deleted
- The activity log
With an activated licence
- Deleting the images and volumes you ticked
- One-click clean-up: unused images, verified orphan volumes, the build cache and Safe Clean All
- Tearing down a whole Compose project, in order: its containers, then the images only it built, then the volumes only it owns, keeping everything shared with other projects
How the licence works
- One payment, no subscription. One licence activates one Mac.
- Activation happens online: me-digital.ro receives the key, a machine identifier and the Mac's name.
- After activation, the licence is checked on your Mac at every launch, with no internet. When you are online, the app also asks whether the seat is still active.
- Changing Macs? Release the seat from the app on the old Mac and activate the licence on the new one.
Why you can trust it
Four things the app does exactly as described here.
Matched by real identifier, not by name
An image counts as "in use" only if its real identifier shows up among existing containers — running or stopped. A stopped container's image will not disappear from under it.
Five states per volume, not two
A volume can be in use, orphaned with a project label, an anonymous orphan, "disputed" (the app's own scan and Docker's filter disagree — held back from any cleanup until that's resolved), or "unknown" when the inspect was incomplete.
The bug that forced a fix has a test of its own
The suite covers label parsing, image and volume classification — and includes a test written for the base image that had been offered for deletion, so that particular mistake cannot come back.
Update checks are opt-in
The app ships with Sparkle for updates, but automatic checking is off — it only checks when you click "Check for Updates". The other connection is the licence: activation, release and the check at launch.
What it does not do yet
The old product page implied the items below too. In this build, none of them have a line of code.
None of these are part of the app as it stands today.
Requirements
Questions
No. The scan runs locally, through the Docker CLI on your machine, and your Docker state never leaves the Mac. The app contacts me-digital.ro only for the licence (the key, a machine identifier and the Mac's name) and, when you ask, for updates.
No. An image counts as "in use" if its real identifier shows up on a container — running or stopped. The container's or project's name plays no part.
It stays "unknown". The app never assumes a volume is orphaned just because it could not check — that is exactly what would turn a live database volume into a false orphan.
A single payment, no subscription. The launch price, the final price and how many licences are left at the launch price are shown at the top of this page.
Both — the app reads straight from the docker CLI regardless of what is running behind it.
DockerSpace
+ VAT, calculated at checkout for your country
383 licences left at the launch price
How to activate your licence
Open the app, click “Activate licence” at the top of the window, next to Refresh, paste the key from the email and press Activate.
On X
What DockerSpace has posted on X. Each post opens on X.