Share feedback
Answers are generated based on the documentation.

sbx stop

DescriptionStop one or more sandboxes without removing them
Usagesbx stop SANDBOX [SANDBOX...]

Description

Stop one or more running sandboxes without removing them. Or — with --cloud — the cloud sandbox ID (sbx_*) or name from "sbx --cloud ls".

Stopped sandboxes retain their state and can be restarted with "sbx run".

With --cloud, stop suspends each sandbox in place: its full state (memory + disk) is preserved, the host is released, and the sandbox keeps its ID. Restart it — same ID — by running its agent again ("sbx --cloud run ") and picking the stopped sandbox from the prompt. A detached run (--detached) creates a new sandbox instead of restarting a stopped one.

Stop does not create a template and does not delete the sandbox. To capture a durable, shareable template from a running sandbox instead, use "sbx --cloud template save SANDBOX TAG" (which leaves the sandbox running).

Global options

OptionDefaultDescription
--cloudDispatch to Docker Cloud Sandboxes API instead of local sandboxd (supported by a growing set of verbs — run 'sbx --cloud --help' for the current list)
--cloud-api-urlhttps://api.sandboxes-cloud.docker.comCloud Sandboxes API base URL; only used with --cloud. Defaults to prod (https://api.sandboxes-cloud.docker.com). Set DOCKER_CLOUD_API_URL or pass this flag to override; a legacy value ending in /v1 is accepted.
-D, --debugEnable debug logging