Share feedback
Answers are generated based on the documentation.

sbx stop

内容説明Stop one or more sandboxes without removing them
利用方法sbx 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. Stop returns once the request is accepted. Watch the sandbox reach the stopped state with "sbx --cloud ls". Restart it — same ID — with "sbx --cloud attach SANDBOX", with "sbx --cloud run AGENT --name NAME" (also non-interactively with --detached), or by running its agent again and picking it from the prompt.

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

オプションデフォルト内容説明
--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)
-D, --debugEnable debug logging