SandboxesLifecycle

Reboot a sandbox

Cold-reboot a running sandbox in order. The VM stops and starts again from the same disk on the same node.

  • First the guest stops its processes (SIGTERM, then SIGKILL a few seconds later) and flushes its file system.
  • In-memory state and running processes are lost. Recently written files survive. The disk and the IP stay.
  • If the guest does not answer within a few seconds, the reboot falls back to a hard reset. Then un-synced writes can be lost.
  • A pending resize applies on reboot.

For an unconditional hard reset, use reset-sandbox.

PUT
/v1/sandboxes/{idOrName}/reboot
AuthorizationBearer <token>

API key starting with tektona_. Create one at app-dev.tektona.ai under API Keys.

In: header

Path Parameters

idOrName*string

Sandbox ID (ULID) or name

Query Parameters

org?string

Required when the path names the sandbox by name.

project?string

Required when the path names the sandbox by name.

Response Body

application/json

application/problem+json

curl -X PUT "https://example.com/v1/sandboxes/string/reboot"
{  "id": "string",  "state": "creating"}