Reset a sandbox
Hard-reset a running sandbox — like pulling the power. Unlike reboot-sandbox the guest gets no shutdown signal and its filesystem is not flushed first, so recently written, un-synced files may be lost. The VM restarts from the same disk on the same node; the disk and IP are preserved. A pending resize applies on reset.
Authorization
apiKey API key starting with tektona_. Create one at app-dev.tektona.ai under API Keys.
In: header
Path Parameters
Sandbox ID (ULID) or name
Query Parameters
Required when the path names the sandbox by name.
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/reset"{ "id": "string", "state": "creating"}{ "detail": "Property foo is required but is missing.", "errors": [ { "location": "string", "message": "string", "value": null } ], "instance": "https://example.com/error-log/abc123", "status": 400, "title": "Bad Request", "type": "https://example.com/errors/example"}Reboot a sandbox PUT
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`.
Resize a sandbox PUT
Change the CPU, memory, or disk allocation of a sandbox. Only provided fields change. - Disk only grows, and grows at once. - CPU and memory grow live on a running sandbox that supports it. Otherwise they apply on the next reboot. - Set `mode` to `live` to fail instead of waiting, or to `deferred` to always wait for the reboot. - A live resize only grows. To shrink memory, set `force`. The change applies on the next reboot. A refusal carries its cause code in the problem type: - 409 for `no_capacity`, `claim_failed`, `resize_in_flight` and `disk_resize_failed`. Nothing changed. - 422 for `shrink_unsupported`, `not_running`, `no_hotplug_limits`, `above_hotplug_limit` or another runner code. - 502 for `live_resize_unknown`: the dispatch came back without a decision, and the change waits as pending.