Sandbox.run(). It’s for developers who have already created a basic sandbox and want to control the container image, resource allocation, and pre-populated files for their workload.
Pass configuration to Sandbox.run()
Configuration options control how the sandbox is provisioned. Pass them as keyword arguments directly to Sandbox.run():
Resources
Configure CPU and memory to match your workload’s needs and avoid over-provisioning or under-provisioning. UseResourceOptions to set requests and limits:
ResourceOptions uses Kubernetes resource syntax:
| Resource | Format | Examples |
|---|---|---|
| CPU | Cores or millicores | "1", "2", "500m" (0.5 CPU) |
| Memory | Bytes with unit suffix | "512Mi", "1Gi", "2Gi" |
Mounted files
Mounted files let you ship configuration, scripts, or other static content into the sandbox before it starts, so your workload has what it needs the moment it runs. Pre-populate files at sandbox startup:write_file() for files that need modification.
Next steps
You now have a sandbox that starts with the container image, resource allocation, and pre-mounted files your workload requires. For reusable configuration across multiple sandboxes, useSandboxDefaults. See the sandbox configuration guide for all ResourceOptions fields, GPU resources, QoS classes, and config-library interop.