What accumulates
When to clean up
- Build failures mentioning disk space — Docker’s storage driver has a configurable cap. When reached, builds fail with
no space left on deviceor similar errors. - Docker Desktop warnings — Docker Desktop shows disk usage in Settings > Resources. If the virtual disk is near its limit, clawker builds will fail.
- Slow builds — An oversized build cache can degrade BuildKit performance.
- General housekeeping — periodic cleanup prevents surprise failures during time-sensitive work.
Cleanup commands
Clawker-managed resources
Clawker labels all its resources (dev.clawker.*), so its own prune commands only affect clawker resources:
Docker-wide cleanup
When clawker-specific cleanup isn’t enough, use Docker’s built-in commands to reclaim space from all Docker resources — not just clawker’s:Checking disk usage
Recommended routine
There’s no need for a strict schedule — just prune when disk usage is becoming a problem or before it does. A reasonable habit:- Run
docker system dfto see where space is going - Start with
clawker image prune— old images are usually the biggest win - If builds are still failing, run
docker builder pruneto clear the BuildKit cache - Use
docker system pruneas a last resort for a broader sweep