Docker Container Cleaner
ReviewAudited by ClawScan on May 10, 2026.
Overview
This appears to be a straightforward Docker cleanup tool, but it can permanently remove Docker resources and may require Docker-level privileges.
Use this only when you intentionally want to clean Docker resources. Start with `status` or `--dry-run`, avoid `--force`/`--yes` unless you are certain, and be especially careful with volumes or production Docker hosts.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Running cleanup, especially with `--all`, `--force`, or `--yes`, can permanently remove stopped containers, unused images, volumes, or networks.
The tool exposes Docker prune operations, including prompt-skipping modes. This is central to its stated cleanup purpose, but the actions can delete local Docker resources.
`--force`: Skip confirmation prompts ... Uses `docker container prune` ... `docker volume prune` ... `docker network prune`
Run `status` or `--dry-run` first, avoid force/no-interactive modes unless you are sure, and back up important Docker volumes before pruning.
The preview may not be a perfect inventory of what Docker will prune, which matters for volume cleanup because volumes can contain data.
The visible code acknowledges simplified unused-volume detection, so status or preview counts may be approximate even though actual deletion is delegated to Docker prune.
# Check for unused volumes (simplified - in real implementation would check mount points) ... unused_count = len(all_volumes)
Manually inspect important volumes/networks and keep backups before using volume or all-resource cleanup.
If run with Docker or sudo privileges, the tool can modify Docker resources for the host environment.
Docker daemon access can be powerful on the host. The requirement is disclosed and expected for Docker cleanup, but users should recognize the privilege boundary.
Some operations may require `sudo` or membership in the `docker` group.
Run it only in Docker environments you control, avoid using it blindly on production hosts, and prefer a least-privileged Docker setup where possible.
It may be harder to independently verify the publisher or upstream maintenance history.
The registry metadata does not provide an upstream project URL or source provenance. The artifacts include code and no automatic install script, so this is a provenance note rather than evidence of hidden behavior.
Source: unknown; Homepage: none
Review the included script before use, especially because it performs destructive Docker cleanup.