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.
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/reboot"{ "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"}Pause a sandbox PUT
Pause a running sandbox via hibernate or suspend mode.
Reset a sandbox PUT
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.