​

Usage

helix stop [INSTANCE]

​

Arguments

​

Options

​

Behavior

• helix stop is idempotent — if the instance is not running, the CLI exits successfully without error.
• Default in-memory data is wiped when the container is removed.
• For disk-mode instances, helix stop removes the Helix and SeaweedFS containers, and any MinIO sidecar left by an older CLI, but keeps the persistent local volumes. Use helix prune to delete disk-mode data.
• The disk-cache volume of a disk-mode or S3 instance is kept too, so the next start reads recently used data locally.
• Remote S3 data is never touched.
• The instance’s Explorer container, when one is running, is stopped too. Failing to remove it never fails the stop: the CLI prints a warning with the cause and suggests helix explorer <instance> --stop to retry.

​

Examples

# Stop the default 'dev' instance
helix stop dev

# Stop 'dev' or the only local instance, or pick one
helix stop

# Safe to call in scripts even if the instance is already stopped
helix stop staging

​

Related

• helix start — start a local instance.
• helix restart — restart a local instance.
• helix prune — remove all Helix-owned local state for an instance.