sincecutoff.com
/v1/json /v1/md llms.txt
← all changes

render ea sandboxes snapshot commands create, get, list, and restore sandboxes

Introduced 2026-09-10 · score 0.97

HOW TO USE IT

When a running sandbox needs preserving, create a snapshot and poll its status with `get` until it is `available`. Then restore it as a new sandbox with `--snapshot-id`; snapshots and restored sandboxes must use the source sandbox’s group.

render ea sandboxes snapshots create <sandboxId> render ea sandboxes snapshots get <snapshotId> render ea sandboxes snapshots list
render ea sandboxes create --snapshot-id <snapshotId>

WHY THIS HELPS

When maintaining a repository that uses Render sandboxes, snapshot a running sandbox and restore a sandbox from that snapshot.

REQUIREMENTS AND LIMITATIONS

  • Version: v2.27.0
  • <sandboxId> (required): ID of the running sandbox to snapshot.
  • <snapshotId> (required): Snapshot ID to retrieve or restore; restore requires an available snapshot.
  • --snapshot-id (required): Start the new sandbox from this snapshot; it must be available and in the same sandbox group. A runtime snapshot requires `--plan` matching its plan.
  • --kind: Snapshot kind: `filesystem` (default) or `runtime`.
  • --group: Sandbox group for `get` or `list`; defaults to the active workspace’s default group.
  • --status: For `list`, repeatable filter: `creating`, `available`, or `failed`.
  • Prerequisite: Render Sandboxes must be enabled for the workspace; docs say sandboxes require a valid Render API key and workspace ID.
  • Prerequisite: The current quickstart requires Render CLI 2.28.0 or later.
  • Docs conflict: Version discrepancy: release v2.27.0 says these snapshot commands and `--snapshot-id` were added in v2.27.0, while the current Render quickstart states CLI 2.28.0 or later is required. The cited current docs do not establish v2.27.0-specific command behavior.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card