bhatti snapshot resume
Resume a named snapshot into a new sandbox.
Synopsis
Section titled “Synopsis”bhatti snapshot resume <snapshot-name> [—name <new-sandbox-name>]
Description
Section titled “Description”Creates a brand-new sandbox by restoring the snapshot’s memory, CPU, and disk state. Running processes pick up exactly where they left off; open file descriptors are still open; in-memory data structures are intact.
The new sandbox gets a new ID and a new IP. Persistent volumes are not re-attached — re-attach them with the same --volume semantics if needed.
--name is optional. Without it, a name is generated from the snapshot’s source sandbox plus a random suffix.
You can resume the same snapshot multiple times — each call produces a fresh sandbox with the same starting state. Useful for fork-and-experiment workflows.
Examples
Section titled “Examples”# Resume into a sandbox with a specific namebhatti snapshot resume pre-experiment --name dev-restoredabc123 dev-restored 192.168.137.42# Auto-generated name (source sandbox + suffix)bhatti snapshot resume pre-experiment# Stamp out parallel copies for an A/B testbhatti snapshot resume base --name worker-abhatti snapshot resume base --name worker-bbhatti snapshot resume base --name worker-cOptions
Section titled “Options”| Flag | Default | Description |
|---|---|---|
--name <string> | auto-generated | Name for the new sandbox. |
See Global flags for --url, --token, --json, --timing, --data-dir.
See also
Section titled “See also”bhatti snapshot create— make the snapshotbhatti snapshot list— find snapshot names- API:
POST /snapshots/:name/resume