DeployCLI Reference
eda prune
Clean up dangling images, BuildKit build cache, and stopped containers on the VPS
The eda prune command reclaims VPS disk space by pruning orphaned Docker build caches, intermediate layers, dangling image tags, and terminated candidate containers.
eda prune [options]
explita deploy prune [options]1. Options
| Flag | Shorthand | Type | Description |
|---|---|---|---|
--all | -a | Boolean | Also prune all unused Docker images and paused/stopped application containers. |
--help | -h | Boolean | Display usage instructions and options. |
2. Standard Prune
Running eda prune without flags performs a safe cleanup of non-essential temporary Docker build resources:
eda pruneWhat Gets Cleaned:
- BuildKit Cache: Leftover image layer compilation artifacts from
docker build. - Dangling Images: Untagged
<none>:<none>images replaced during zero-downtime releases. - Dead Containers: Containers that completed execution (such as one-off
eda execcommands or completed pre-deploy hooks). - Orphaned Networks: Unused Docker network bridges.
Active running application containers and their current image tags are never touched.
3. Aggressive Deep Prune (--all)
To reclaim maximum disk space on a heavily utilized VPS:
eda prune --allIn addition to the standard cleanup, --all removes:
- All cached Docker images not currently bound to an active, running container.
- Stopped application containers preserved from older rollback targets.
[!TIP] Run
eda pruneperiodically or ifeda doctoralerts you that host disk space utilization has exceeded 80%.