Create an ephemeral or named sandbox.
snapshot_id in the request body. Tensorlake restores the captured filesystem and memory state, and reuses the image, resources, entrypoint, and secrets from the snapshot unless you explicitly override them.
image, resources, timeout_secs, entrypoint, network, allow_unauthenticated_access, exposed_ports, template_id, and name when booting from a snapshot.
For the full request and response schema of POST /sandboxes, see Create Sandbox. For the end-to-end snapshot workflow, see Snapshots.Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Optional sandbox image name to boot from. When omitted, Tensorlake uses the default managed environment. This can also be a registered Sandbox Image name.
Secret names to inject into the sandbox.
Sandbox timeout in seconds. 0 disables the timeout.
x >= 0Optional command to run when the sandbox starts.
Snapshot to restore from.
Allow sandbox ingress to route requests without validating auth credentials. The legacy request alias allow_unauthenticated_proxy_access is also accepted.
Additional sandbox ports that public ingress may route to. When omitted, only the management port 9501 is routable.
1 <= x <= 65535Template identifier to associate with the launched sandbox.
Optional user-provided sandbox name. When set, the sandbox is named and supports suspend/resume. When omitted, the sandbox is ephemeral.
Sandbox created successfully