Reference
Remove Helix-owned local containers, networks, disk-mode volumes, and per-instance workspace state.
Local only; the instance stays in helix.toml.
Usage
Arguments
Options
Behavior
helix prune only touches resources the CLI manages:
- The container named
helix-<project>-<instance>. - The disk-mode SeaweedFS sidecar, network, and persistent volume when present, plus any MinIO sidecar and volume left by an older CLI.
- The disk-cache volume of a disk-mode or S3 instance.
- The per-instance directory under
.helix/.
docker system prune or podman system prune, and it never deletes remote S3
object-store data.
-
helix prune <instance>removes resources without confirmation, including persisted disk-mode data. -
helix prune --allprints a warning and asks for confirmation in a TTY. Without a TTY, or with--json, it refuses to run without--yes: -
If nothing was found to prune for an instance, the CLI prints
No local runtime resources found for <instance>and exits successfully. -
With
--json, prints one object for the whole run:{"pruned":[{"instance":"dev","removed":true}]}.
Examples
Related
helix stop— stop an instance but keep disk-mode data.helix delete— also remove the instance fromhelix.toml.helix start— start a fresh instance after pruning.