Linux Sandboxes
Daytona provides Linux sandboxes as the default sandbox for AI agents. A Linux sandbox is an isolated runtime environment you manage programmatically to run code. Each sandbox has a dedicated filesystem, network stack, and allocated vCPU, RAM, and disk. Agents and developers can install packages, run servers, compile code, and manage processes.
Linux sandboxes run as containers or as Linux virtual machines (VMs). The snapshot sets the sandbox class, and both classes use the same SDKs, CLI, and API. Linux sandboxes start from a snapshot or a Docker image, keep their filesystem across stop and start, and are deleted when a timeout elapses or on request.
| Term | Description |
|---|---|
| Sandbox | An isolated Linux environment created on demand to run code. |
| Container | A sandbox that runs as a Linux container and shares the kernel of the host. The default sandbox class. |
| Linux VM | A sandbox that runs as a virtual machine with its own Linux kernel. The hardware enforces the boundary between sandboxes. |
| Sandbox class | The runtime of a Linux sandbox: container or Linux VM. The snapshot sets the class. |
| Image | A packaged filesystem that defines the software a sandbox starts with. Container sandboxes can start from a Docker image. |
| Snapshot | A pre-configured template that new sandboxes start from. |
| Toolbox | The Daytona daemon inside the sandbox that serves file, Git, and process requests. |
Use cases
Section titled “Use cases”Linux sandboxes are used wherever code must run in a real environment, but you cannot trust the code or you cannot afford for it to affect anything else.
- Code execution for AI agents: an agent writes code, runs it in a sandbox, reads the output, and decides what to do next. The sandbox gives the agent a real shell and filesystem while keeping its actions away from your infrastructure.
- Coding agents: an agent clones a repository, installs dependencies, edits files, runs the test suite, and pushes a branch, all inside one sandbox.
- Reinforcement learning (RL) and evaluation: each episode or test case gets a clean, identical machine created from a shared snapshot, so results do not depend on leftover state and each environment stays cheap.
- Untrusted user code: online coding platforms, grading systems, code interpreters, and plugin hosts run code submitted by users or generated by a model without exposing other users or the service.
- Computer-use agents: an agent operates a graphical desktop, a browser, or desktop applications through screenshots and input events.
- Development environments: a developer gets a preconfigured machine from an image, connects over SSH or from an editor, and previews web applications through a URL.
- Long-lived and branching agent sessions: a Linux VM sandbox pauses when the agent goes idle and resumes with its processes and memory intact, and is forked to try several approaches from the same point.
Create a Linux sandbox
Section titled “Create a Linux sandbox”Create a sandbox.
- Go to Daytona Sandboxes ↗
- Click
- Click
from daytona import Daytona
daytona = Daytona()sandbox = daytona.create()import { Daytona } from '@daytona/sdk'
const daytona = new Daytona()const sandbox = await daytona.create()require 'daytona'
daytona = Daytona::Daytona.newsandbox = daytona.createpackage main
import ( "context"
"github.com/daytona/clients/sdk-go/pkg/daytona")
func main() { client, _ := daytona.NewClient() ctx := context.Background() _, _ = client.Create(ctx, nil)}import io.daytona.sdk.Daytona;import io.daytona.sdk.Sandbox;
public class App { public static void main(String[] args) { try (Daytona daytona = new Daytona()) { Sandbox sandbox = daytona.create(); } }}daytona createcurl 'https://app.daytona.io/api/sandbox' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{}'Create a Linux VM sandbox
Section titled “Create a Linux VM sandbox”Create a Linux VM sandbox.
Create a Linux VM sandbox.
- Go to Daytona Snapshots ↗
- Click
- Enter the , for example
my-vm-snapshot - Enter the , for example
ubuntu:22.04 - Select :
LINUX_VM - Click
- Go to Daytona Sandboxes ↗
- Click
- Select the VM , for example
my-vm-snapshot - Click
from daytona import ( Daytona, CreateSnapshotParams, CreateSandboxFromSnapshotParams, SandboxClass,)
daytona = Daytona()
# Create a Linux VM snapshotdaytona.snapshot.create( CreateSnapshotParams( name="my-vm-snapshot", image="ubuntu:22.04", sandbox_class=SandboxClass.LINUX_VM, ))
# Create a Linux VM sandbox from the snapshotsandbox = daytona.create(CreateSandboxFromSnapshotParams(snapshot="my-vm-snapshot"))import { Daytona, SandboxClass } from '@daytona/sdk'
const daytona = new Daytona()
// Create a Linux VM snapshotawait daytona.snapshot.create({ name: 'my-vm-snapshot', image: 'ubuntu:22.04', sandboxClass: SandboxClass.LINUX_VM,})
// Create a Linux VM sandbox from the snapshotconst sandbox = await daytona.create({ snapshot: 'my-vm-snapshot' })require 'daytona'
daytona = Daytona::Daytona.new
# Create a Linux VM snapshotdaytona.snapshot.create( Daytona::CreateSnapshotParams.new( name: 'my-vm-snapshot', image: 'ubuntu:22.04', sandbox_class: DaytonaApiClient::SandboxClass::LINUX_VM ))
# Create a Linux VM sandbox from the snapshotsandbox = daytona.create(Daytona::CreateSandboxFromSnapshotParams.new(snapshot: 'my-vm-snapshot'))package main
import ( "context"
"github.com/daytona/clients/sdk-go/pkg/daytona" "github.com/daytona/clients/sdk-go/pkg/types")
func main() { client, _ := daytona.NewClient() ctx := context.Background()
// Create a Linux VM snapshot sandboxClass := types.SandboxClassLinuxVM _, logCh, _ := client.Snapshot.Create(ctx, &types.CreateSnapshotParams{ Name: "my-vm-snapshot", Image: "ubuntu:22.04", SandboxClass: &sandboxClass, }) for range logCh { }
// Create a Linux VM sandbox from the snapshot _, _ = client.Create(ctx, types.SnapshotParams{ Snapshot: "my-vm-snapshot", })}import io.daytona.sdk.Daytona;import io.daytona.sdk.Sandbox;import io.daytona.api.client.model.SandboxClass;import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;
public class App { public static void main(String[] args) { try (Daytona daytona = new Daytona()) { // Create a Linux VM snapshot daytona.snapshot().create("my-vm-snapshot", "ubuntu:22.04", SandboxClass.LINUX_VM);
// Create a Linux VM sandbox from the snapshot CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams(); params.setSnapshot("my-vm-snapshot"); Sandbox sandbox = daytona.create(params); } }}# Create a Linux VM snapshotdaytona snapshot create my-vm-snapshot --image ubuntu:22.04 --sandbox-class linux-vm
# Create a Linux VM sandbox from the snapshotdaytona create --snapshot my-vm-snapshot# Create a Linux VM snapshotcurl 'https://app.daytona.io/api/snapshots' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{ "name": "my-vm-snapshot", "imageName": "ubuntu:22.04", "sandboxClass": "linux-vm"}'
# Create a Linux VM sandbox from the snapshotcurl 'https://app.daytona.io/api/sandbox' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{ "snapshot": "my-vm-snapshot"}'Create a Linux VM sandbox from a default snapshot.
- Go to Daytona Sandboxes ↗
- Click
- Select a VM :
daytona-vm-small,daytona-vm-medium, ordaytona-vm-large - Click
from daytona import Daytona, CreateSandboxFromSnapshotParams
daytona = Daytona()sandbox = daytona.create(CreateSandboxFromSnapshotParams(snapshot="daytona-vm-small"))import { Daytona } from '@daytona/sdk'
const daytona = new Daytona()const sandbox = await daytona.create({ snapshot: 'daytona-vm-small' })require 'daytona'
daytona = Daytona::Daytona.newsandbox = daytona.create( Daytona::CreateSandboxFromSnapshotParams.new(snapshot: 'daytona-vm-small'))package main
import ( "context"
"github.com/daytona/clients/sdk-go/pkg/daytona" "github.com/daytona/clients/sdk-go/pkg/types")
func main() { client, _ := daytona.NewClient() ctx := context.Background() _, _ = client.Create(ctx, types.SnapshotParams{ Snapshot: "daytona-vm-small", })}import io.daytona.sdk.Daytona;import io.daytona.sdk.Sandbox;import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;
public class App { public static void main(String[] args) { try (Daytona daytona = new Daytona()) { CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams(); params.setSnapshot("daytona-vm-small"); Sandbox sandbox = daytona.create(params); } }}daytona create --snapshot daytona-vm-smallcurl 'https://app.daytona.io/api/sandbox' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{ "snapshot": "daytona-vm-small"}'Nested virtualization
Section titled “Nested virtualization”Daytona provides nested virtualization for Linux VM sandboxes. Nested virtualization exposes KVM (/dev/kvm) inside the guest, so the sandbox can run its own virtual machines with hardware acceleration.
from daytona import Daytona, CreateSandboxFromSnapshotParams
daytona = Daytona()sandbox = daytona.create( CreateSandboxFromSnapshotParams( snapshot="daytona-vm-small", kvm=True, ))import { Daytona } from '@daytona/sdk'
const daytona = new Daytona()const sandbox = await daytona.create({ snapshot: 'daytona-vm-small', kvm: true,})require 'daytona'
daytona = Daytona::Daytona.newsandbox = daytona.create( Daytona::CreateSandboxFromSnapshotParams.new( snapshot: 'daytona-vm-small', kvm: true ))package main
import ( "context"
"github.com/daytona/clients/sdk-go/pkg/daytona" "github.com/daytona/clients/sdk-go/pkg/types")
func main() { client, _ := daytona.NewClient() ctx := context.Background() params := types.SnapshotParams{ SandboxBaseParams: types.SandboxBaseParams{ Kvm: true, }, Snapshot: "daytona-vm-small", } _, _ = client.Create(ctx, params)}import io.daytona.sdk.Daytona;import io.daytona.sdk.Sandbox;import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;
public class App { public static void main(String[] args) { try (Daytona daytona = new Daytona()) { CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams(); params.setSnapshot("daytona-vm-small"); params.setKvm(true); Sandbox sandbox = daytona.create(params); } }}daytona create --snapshot daytona-vm-small --kvmcurl 'https://app.daytona.io/api/sandbox' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{ "snapshot": "daytona-vm-small", "kvm": true}'Filesystem persistence
Section titled “Filesystem persistence”Filesystem persistence keeps the contents of a sandbox’s disk: files, installed packages, cloned repositories, and build artifacts. A sandbox with a preserved filesystem starts with its environment intact, with nothing to reinstall or rebuild.
Linux sandboxes preserve their filesystem across stop and start, archive, and filesystem snapshots created from a sandbox. An ephemeral sandbox is deleted on stop, so its filesystem is not kept. The sandbox classes differ in where the preserved filesystem is stored while the sandbox is stopped:
| Sandbox class | Filesystem persistence |
|---|---|
| Container | Filesystem is preserved through stop and start: it stays on the runner and counts against disk quota while stopped. Archive moves it to object storage and frees the quota, and starting an archived sandbox restores it. Use filesystem snapshots to capture the filesystem. |
| Linux VM | Filesystem is preserved through stop and start: stopping offloads it to nearby storage and releases disk quota, starting restores it. Archive is not needed. Use filesystem snapshots to capture the filesystem. |
from daytona import Daytona
daytona = Daytona()sandbox = daytona.create()
# Write a file to the filesystemsandbox.fs.upload_file(b"done", "setup.log")
# Stop clears memory and keeps the filesystemsandbox.stop()
# Start boots the sandbox from its filesystemsandbox.start()content = sandbox.fs.download_file("setup.log")print(content.decode()) # doneimport { Daytona } from '@daytona/sdk'
const daytona = new Daytona()const sandbox = await daytona.create()
// Write a file to the filesystemawait sandbox.fs.uploadFile(Buffer.from('done'), 'setup.log')
// Stop clears memory and keeps the filesystemawait sandbox.stop()
// Start boots the sandbox from its filesystemawait sandbox.start()const content = await sandbox.fs.downloadFile('setup.log')console.log(content.toString()) // donerequire 'daytona'
daytona = Daytona::Daytona.newsandbox = daytona.create
# Write a file to the filesystemsandbox.fs.upload_file('done', 'setup.log')
# Stop clears memory and keeps the filesystemsandbox.stop
# Start boots the sandbox from its filesystemsandbox.startcontent = sandbox.fs.download_file('setup.log')puts content # donepackage main
import ( "context" "fmt"
"github.com/daytona/clients/sdk-go/pkg/daytona" "github.com/daytona/clients/sdk-go/pkg/types")
func main() { client, _ := daytona.NewClient() ctx := context.Background() sandbox, err := client.Create(ctx, types.SnapshotParams{}) if err != nil { panic(err) }
// Write a file to the filesystem if err := sandbox.FileSystem.UploadFile(ctx, []byte("done"), "setup.log"); err != nil { panic(err) }
// Stop clears memory and keeps the filesystem if err := sandbox.Stop(ctx); err != nil { panic(err) }
// Start boots the sandbox from its filesystem if err := sandbox.Start(ctx); err != nil { panic(err) } content, err := sandbox.FileSystem.DownloadFile(ctx, "setup.log", nil) if err != nil { panic(err) } fmt.Println(string(content)) // done}import io.daytona.sdk.Daytona;import io.daytona.sdk.Sandbox;
public class App { public static void main(String[] args) { try (Daytona daytona = new Daytona()) { Sandbox sandbox = daytona.create();
// Write a file to the filesystem sandbox.fs.uploadFile("done".getBytes(), "setup.log");
// Stop clears memory and keeps the filesystem sandbox.stop();
// Start boots the sandbox from its filesystem sandbox.start(); byte[] content = sandbox.fs.downloadFile("setup.log"); System.out.println(new String(content)); // done } }}daytona create
# Write a file to the filesystemdaytona exec [SANDBOX_ID] -- sh -c 'echo done > setup.log'
# Stop clears memory and keeps the filesystemdaytona stop [SANDBOX_ID]
# Start boots the sandbox from its filesystemdaytona start [SANDBOX_ID]daytona exec [SANDBOX_ID] -- cat setup.logcurl 'https://app.daytona.io/api/sandbox' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{}'
# Write a file to the filesystemcurl 'https://proxy.app.daytona.io/toolbox/{sandboxId}/files/upload-v2?path=setup.log' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY' \ --form 'file=@setup.log'
# Stop clears memory and keeps the filesystemcurl 'https://app.daytona.io/api/sandbox/{sandboxId}/stop' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY'
# Start boots the sandbox from its filesystemcurl 'https://app.daytona.io/api/sandbox/{sandboxId}/start' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY'
curl 'https://proxy.app.daytona.io/toolbox/{sandboxId}/files/download?path=setup.log' \ --header 'Authorization: Bearer YOUR_API_KEY'from daytona import Daytona, CreateSandboxFromSnapshotParams
daytona = Daytona()sandbox = daytona.create(CreateSandboxFromSnapshotParams(snapshot="daytona-vm-small"))
# Write a file to the filesystemsandbox.fs.upload_file(b"done", "setup.log")
# Stop clears memory and moves the filesystem to nearby storagesandbox.stop()
# Start restores the filesystem and boots the sandboxsandbox.start()content = sandbox.fs.download_file("setup.log")print(content.decode()) # doneimport { Daytona } from '@daytona/sdk'
const daytona = new Daytona()const sandbox = await daytona.create({ snapshot: 'daytona-vm-small' })
// Write a file to the filesystemawait sandbox.fs.uploadFile(Buffer.from('done'), 'setup.log')
// Stop clears memory and moves the filesystem to nearby storageawait sandbox.stop()
// Start restores the filesystem and boots the sandboxawait sandbox.start()const content = await sandbox.fs.downloadFile('setup.log')console.log(content.toString()) // donerequire 'daytona'
daytona = Daytona::Daytona.newsandbox = daytona.create(Daytona::CreateSandboxFromSnapshotParams.new(snapshot: 'daytona-vm-small'))
# Write a file to the filesystemsandbox.fs.upload_file('done', 'setup.log')
# Stop clears memory and moves the filesystem to nearby storagesandbox.stop
# Start restores the filesystem and boots the sandboxsandbox.startcontent = sandbox.fs.download_file('setup.log')puts content # donepackage main
import ( "context" "fmt"
"github.com/daytona/clients/sdk-go/pkg/daytona" "github.com/daytona/clients/sdk-go/pkg/types")
func main() { client, _ := daytona.NewClient() ctx := context.Background() sandbox, err := client.Create(ctx, types.SnapshotParams{Snapshot: "daytona-vm-small"}) if err != nil { panic(err) }
// Write a file to the filesystem if err := sandbox.FileSystem.UploadFile(ctx, []byte("done"), "setup.log"); err != nil { panic(err) }
// Stop clears memory and moves the filesystem to nearby storage if err := sandbox.Stop(ctx); err != nil { panic(err) }
// Start restores the filesystem and boots the sandbox if err := sandbox.Start(ctx); err != nil { panic(err) } content, err := sandbox.FileSystem.DownloadFile(ctx, "setup.log", nil) if err != nil { panic(err) } fmt.Println(string(content)) // done}import io.daytona.sdk.Daytona;import io.daytona.sdk.Sandbox;import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;
public class App { public static void main(String[] args) { try (Daytona daytona = new Daytona()) { CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams(); params.setSnapshot("daytona-vm-small"); Sandbox sandbox = daytona.create(params);
// Write a file to the filesystem sandbox.fs.uploadFile("done".getBytes(), "setup.log");
// Stop clears memory and moves the filesystem to nearby storage sandbox.stop();
// Start restores the filesystem and boots the sandbox sandbox.start(); byte[] content = sandbox.fs.downloadFile("setup.log"); System.out.println(new String(content)); // done } }}daytona create --snapshot daytona-vm-small
# Write a file to the filesystemdaytona exec [SANDBOX_ID] -- sh -c 'echo done > setup.log'
# Stop clears memory and moves the filesystem to nearby storagedaytona stop [SANDBOX_ID]
# Start restores the filesystem and boots the sandboxdaytona start [SANDBOX_ID]daytona exec [SANDBOX_ID] -- cat setup.logcurl 'https://app.daytona.io/api/sandbox' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{"snapshot": "daytona-vm-small"}'
# Write a file to the filesystemcurl 'https://proxy.app.daytona.io/toolbox/{sandboxId}/files/upload-v2?path=setup.log' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY' \ --form 'file=@setup.log'
# Stop clears memory and moves the filesystem to nearby storagecurl 'https://app.daytona.io/api/sandbox/{sandboxId}/stop' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY'
# Start restores the filesystem and boots the sandboxcurl 'https://app.daytona.io/api/sandbox/{sandboxId}/start' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY'
curl 'https://proxy.app.daytona.io/toolbox/{sandboxId}/files/download?path=setup.log' \ --header 'Authorization: Bearer YOUR_API_KEY'Memory persistence
Section titled “Memory persistence”Memory persistence keeps the runtime state of a sandbox: running processes, open connections, and everything loaded in RAM. A sandbox with preserved memory continues from the point it was frozen, with processes still running, instead of starting from a clean boot.
Linux VM sandboxes preserve their memory across pause and resume, memory snapshots created from a sandbox, and forks. Memory state is cleared on every stop. The sandbox classes differ in whether memory can be preserved without keeping the sandbox running:
| Sandbox class | Memory persistence |
|---|---|
| Container | Memory persists only while the sandbox is running. Set the auto-stop interval to zero to run indefinitely, or relaunch processes after each start. Pause is not supported. |
| Linux VM | Memory is preserved through pause and resume: pausing freezes the VM with memory intact, resuming continues all processes from the point they were frozen. Use memory snapshots or forks to capture memory. |
The following example creates a Linux VM sandbox. Pause requires a non-ephemeral Linux VM sandbox in the Started state.
from daytona import Daytona, CreateSandboxFromSnapshotParams, SessionExecuteRequest
daytona = Daytona()sandbox = daytona.create(CreateSandboxFromSnapshotParams(snapshot="daytona-vm-small"))
# Start a process that runs in the backgroundsandbox.process.create_session("keepalive")response = sandbox.process.execute_session_command( "keepalive", SessionExecuteRequest(command="sleep 3600", run_async=True),)
# Pause keeps the filesystem and memorysandbox.pause()
# Start resumes every process from the point where the sandbox pausedsandbox.start()command = sandbox.process.get_session_command("keepalive", response.cmd_id)print(command.exit_code) # None: the process is still runningimport { Daytona } from '@daytona/sdk'
const daytona = new Daytona()const sandbox = await daytona.create({ snapshot: 'daytona-vm-small' })
// Start a process that runs in the backgroundawait sandbox.process.createSession('keepalive')const response = await sandbox.process.executeSessionCommand('keepalive', { command: 'sleep 3600', runAsync: true,})
// Pause keeps the filesystem and memoryawait sandbox.pause()
// Start resumes every process from the point where the sandbox pausedawait sandbox.start()const command = await sandbox.process.getSessionCommand('keepalive', response.cmdId)console.log(command.exitCode) // undefined: the process is still runningrequire 'daytona'
daytona = Daytona::Daytona.newsandbox = daytona.create(Daytona::CreateSandboxFromSnapshotParams.new(snapshot: 'daytona-vm-small'))
# Start a process that runs in the backgroundsandbox.process.create_session('keepalive')response = sandbox.process.execute_session_command( session_id: 'keepalive', req: Daytona::SessionExecuteRequest.new(command: 'sleep 3600', run_async: true))
# Pause keeps the filesystem and memorysandbox.pause
# Start resumes every process from the point where the sandbox pausedsandbox.startcommand = sandbox.process.get_session_command(session_id: 'keepalive', command_id: response.cmd_id)puts command.exit_code.inspect # nil: the process is still runningpackage main
import ( "context" "fmt"
"github.com/daytona/clients/sdk-go/pkg/daytona" "github.com/daytona/clients/sdk-go/pkg/types")
func main() { client, _ := daytona.NewClient() ctx := context.Background() sandbox, err := client.Create(ctx, types.SnapshotParams{Snapshot: "daytona-vm-small"}) if err != nil { panic(err) }
// Start a process that runs in the background if err := sandbox.Process.CreateSession(ctx, "keepalive"); err != nil { panic(err) } response, err := sandbox.Process.ExecuteSessionCommand(ctx, "keepalive", "sleep 3600", true, false) if err != nil { panic(err) }
// Pause keeps the filesystem and memory if err := sandbox.Pause(ctx); err != nil { panic(err) }
// Start resumes every process from the point where the sandbox paused if err := sandbox.Start(ctx); err != nil { panic(err) } command, err := sandbox.Process.GetSessionCommand(ctx, "keepalive", response["cmdId"].(string)) if err != nil { panic(err) } fmt.Println(command["exitCode"]) // <nil>: the process is still running}import io.daytona.sdk.Daytona;import io.daytona.sdk.Sandbox;import io.daytona.sdk.model.Command;import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;import io.daytona.sdk.model.SessionExecuteRequest;import io.daytona.sdk.model.SessionExecuteResponse;
public class App { public static void main(String[] args) { try (Daytona daytona = new Daytona()) { CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams(); params.setSnapshot("daytona-vm-small"); Sandbox sandbox = daytona.create(params);
// Start a process that runs in the background sandbox.process.createSession("keepalive"); SessionExecuteResponse response = sandbox.process.executeSessionCommand( "keepalive", new SessionExecuteRequest("sleep 3600", true) );
// Pause keeps the filesystem and memory sandbox.pause();
// Start resumes every process from the point where the sandbox paused sandbox.start(); Command command = sandbox.process.getSessionCommand("keepalive", response.getCmdId()); System.out.println(command.getExitCode()); // null: the process is still running } }}daytona create --snapshot daytona-vm-small
# Pause keeps the filesystem and memorydaytona pause [SANDBOX_ID]
# Start resumes every process from the point where the sandbox pauseddaytona start [SANDBOX_ID]curl 'https://app.daytona.io/api/sandbox' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{"snapshot": "daytona-vm-small"}'
# Start a process that runs in the backgroundcurl 'https://proxy.app.daytona.io/toolbox/{sandboxId}/process/session' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{"sessionId": "keepalive"}'
curl 'https://proxy.app.daytona.io/toolbox/{sandboxId}/process/session/keepalive/exec' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{"command": "sleep 3600", "runAsync": true}'
# Pause keeps the filesystem and memorycurl 'https://app.daytona.io/api/sandbox/{sandboxId}/pause' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY'
# Start resumes every process from the point where the sandbox pausedcurl 'https://app.daytona.io/api/sandbox/{sandboxId}/start' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY'
# The command has no exitCode while the process is still runningcurl 'https://proxy.app.daytona.io/toolbox/{sandboxId}/process/session/keepalive/command/{commandId}' \ --header 'Authorization: Bearer YOUR_API_KEY'Memory snapshot
Section titled “Memory snapshot”A memory snapshot, also called a hot snapshot, saves the filesystem and memory of a started Linux VM sandbox. A sandbox created from a memory snapshot starts with its processes already running. Enable the include memory option when you create the snapshot. Container sandboxes do not support memory snapshots.
A memory snapshot requires a Linux VM sandbox in the Started state. The SDKs do not expose the include memory option, so use the API.
curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/snapshot' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{ "name": "my-vm-snapshot", "includeMemory": true}'Filesystem snapshot
Section titled “Filesystem snapshot”A filesystem snapshot, also called a cold snapshot, saves the filesystem of a stopped Linux sandbox. Both sandbox classes support filesystem snapshots. A snapshot without the include memory option is a filesystem snapshot.
A filesystem snapshot requires a sandbox in the Stopped state. An ephemeral sandbox is deleted on stop, so it cannot take a filesystem snapshot.
from daytona import Daytona, CreateSandboxFromSnapshotParams
daytona = Daytona()sandbox = daytona.create()
# Write a file to the filesystemsandbox.fs.upload_file(b"done", "setup.log")
# A filesystem snapshot requires a stopped sandboxsandbox.stop()sandbox.create_snapshot("my-snapshot")
# A sandbox created from the snapshot starts with the same filesystemnew_sandbox = daytona.create(CreateSandboxFromSnapshotParams(snapshot="my-snapshot"))content = new_sandbox.fs.download_file("setup.log")print(content.decode()) # doneimport { Daytona } from '@daytona/sdk'
const daytona = new Daytona()const sandbox = await daytona.create()
// Write a file to the filesystemawait sandbox.fs.uploadFile(Buffer.from('done'), 'setup.log')
// A filesystem snapshot requires a stopped sandboxawait sandbox.stop()await sandbox.createSnapshot('my-snapshot')
// A sandbox created from the snapshot starts with the same filesystemconst newSandbox = await daytona.create({ snapshot: 'my-snapshot' })const content = await newSandbox.fs.downloadFile('setup.log')console.log(content.toString()) // donerequire 'daytona'
daytona = Daytona::Daytona.newsandbox = daytona.create
# Write a file to the filesystemsandbox.fs.upload_file('done', 'setup.log')
# A filesystem snapshot requires a stopped sandboxsandbox.stopsandbox.create_snapshot(name: 'my-snapshot')
# A sandbox created from the snapshot starts with the same filesystemnew_sandbox = daytona.create(Daytona::CreateSandboxFromSnapshotParams.new(snapshot: 'my-snapshot'))content = new_sandbox.fs.download_file('setup.log')puts content # donepackage main
import ( "context" "fmt"
"github.com/daytona/clients/sdk-go/pkg/daytona" "github.com/daytona/clients/sdk-go/pkg/types")
func main() { client, _ := daytona.NewClient() ctx := context.Background() sandbox, err := client.Create(ctx, types.SnapshotParams{}) if err != nil { panic(err) }
// Write a file to the filesystem if err := sandbox.FileSystem.UploadFile(ctx, []byte("done"), "setup.log"); err != nil { panic(err) }
// A filesystem snapshot requires a stopped sandbox if err := sandbox.Stop(ctx); err != nil { panic(err) } if err := sandbox.CreateSnapshot(ctx, "my-snapshot"); err != nil { panic(err) }
// A sandbox created from the snapshot starts with the same filesystem newSandbox, err := client.Create(ctx, types.SnapshotParams{Snapshot: "my-snapshot"}) if err != nil { panic(err) } content, err := newSandbox.FileSystem.DownloadFile(ctx, "setup.log", nil) if err != nil { panic(err) } fmt.Println(string(content)) // done}import io.daytona.sdk.Daytona;import io.daytona.sdk.Sandbox;import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;
public class App { public static void main(String[] args) { try (Daytona daytona = new Daytona()) { Sandbox sandbox = daytona.create();
// Write a file to the filesystem sandbox.fs.uploadFile("done".getBytes(), "setup.log");
// A filesystem snapshot requires a stopped sandbox sandbox.stop(); sandbox.createSnapshot("my-snapshot");
// A sandbox created from the snapshot starts with the same filesystem CreateSandboxFromSnapshotParams fromSnapshot = new CreateSandboxFromSnapshotParams(); fromSnapshot.setSnapshot("my-snapshot"); Sandbox newSandbox = daytona.create(fromSnapshot); byte[] content = newSandbox.fs.downloadFile("setup.log"); System.out.println(new String(content)); // done } }}curl 'https://app.daytona.io/api/sandbox' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{}'
# Write a file to the filesystemcurl 'https://proxy.app.daytona.io/toolbox/{sandboxId}/files/upload-v2?path=setup.log' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY' \ --form 'file=@setup.log'
# A filesystem snapshot requires a stopped sandboxcurl 'https://app.daytona.io/api/sandbox/{sandboxId}/stop' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY'
curl 'https://app.daytona.io/api/sandbox/{sandboxId}/snapshot' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{ "name": "my-snapshot", "includeMemory": false}'
# A sandbox created from the snapshot starts with the same filesystemcurl 'https://app.daytona.io/api/sandbox' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{"snapshot": "my-snapshot"}'
curl 'https://proxy.app.daytona.io/toolbox/{newSandboxId}/files/download?path=setup.log' \ --header 'Authorization: Bearer YOUR_API_KEY'from daytona import Daytona, CreateSandboxFromSnapshotParams
daytona = Daytona()sandbox = daytona.create(CreateSandboxFromSnapshotParams(snapshot="daytona-vm-small"))
# Write a file to the filesystemsandbox.fs.upload_file(b"done", "setup.log")
# A filesystem snapshot requires a stopped sandboxsandbox.stop()sandbox.create_snapshot("my-vm-snapshot")
# A sandbox created from the snapshot starts with the same filesystemnew_sandbox = daytona.create(CreateSandboxFromSnapshotParams(snapshot="my-vm-snapshot"))content = new_sandbox.fs.download_file("setup.log")print(content.decode()) # doneimport { Daytona } from '@daytona/sdk'
const daytona = new Daytona()const sandbox = await daytona.create({ snapshot: 'daytona-vm-small' })
// Write a file to the filesystemawait sandbox.fs.uploadFile(Buffer.from('done'), 'setup.log')
// A filesystem snapshot requires a stopped sandboxawait sandbox.stop()await sandbox.createSnapshot('my-vm-snapshot')
// A sandbox created from the snapshot starts with the same filesystemconst newSandbox = await daytona.create({ snapshot: 'my-vm-snapshot' })const content = await newSandbox.fs.downloadFile('setup.log')console.log(content.toString()) // donerequire 'daytona'
daytona = Daytona::Daytona.newsandbox = daytona.create(Daytona::CreateSandboxFromSnapshotParams.new(snapshot: 'daytona-vm-small'))
# Write a file to the filesystemsandbox.fs.upload_file('done', 'setup.log')
# A filesystem snapshot requires a stopped sandboxsandbox.stopsandbox.create_snapshot(name: 'my-vm-snapshot')
# A sandbox created from the snapshot starts with the same filesystemnew_sandbox = daytona.create(Daytona::CreateSandboxFromSnapshotParams.new(snapshot: 'my-vm-snapshot'))content = new_sandbox.fs.download_file('setup.log')puts content # donepackage main
import ( "context" "fmt"
"github.com/daytona/clients/sdk-go/pkg/daytona" "github.com/daytona/clients/sdk-go/pkg/types")
func main() { client, _ := daytona.NewClient() ctx := context.Background() sandbox, err := client.Create(ctx, types.SnapshotParams{Snapshot: "daytona-vm-small"}) if err != nil { panic(err) }
// Write a file to the filesystem if err := sandbox.FileSystem.UploadFile(ctx, []byte("done"), "setup.log"); err != nil { panic(err) }
// A filesystem snapshot requires a stopped sandbox if err := sandbox.Stop(ctx); err != nil { panic(err) } if err := sandbox.CreateSnapshot(ctx, "my-vm-snapshot"); err != nil { panic(err) }
// A sandbox created from the snapshot starts with the same filesystem newSandbox, err := client.Create(ctx, types.SnapshotParams{Snapshot: "my-vm-snapshot"}) if err != nil { panic(err) } content, err := newSandbox.FileSystem.DownloadFile(ctx, "setup.log", nil) if err != nil { panic(err) } fmt.Println(string(content)) // done}import io.daytona.sdk.Daytona;import io.daytona.sdk.Sandbox;import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;
public class App { public static void main(String[] args) { try (Daytona daytona = new Daytona()) { CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams(); params.setSnapshot("daytona-vm-small"); Sandbox sandbox = daytona.create(params);
// Write a file to the filesystem sandbox.fs.uploadFile("done".getBytes(), "setup.log");
// A filesystem snapshot requires a stopped sandbox sandbox.stop(); sandbox.createSnapshot("my-vm-snapshot");
// A sandbox created from the snapshot starts with the same filesystem CreateSandboxFromSnapshotParams fromSnapshot = new CreateSandboxFromSnapshotParams(); fromSnapshot.setSnapshot("my-vm-snapshot"); Sandbox newSandbox = daytona.create(fromSnapshot); byte[] content = newSandbox.fs.downloadFile("setup.log"); System.out.println(new String(content)); // done } }}curl 'https://app.daytona.io/api/sandbox' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{"snapshot": "daytona-vm-small"}'
# Write a file to the filesystemcurl 'https://proxy.app.daytona.io/toolbox/{sandboxId}/files/upload-v2?path=setup.log' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY' \ --form 'file=@setup.log'
# A filesystem snapshot requires a stopped sandboxcurl 'https://app.daytona.io/api/sandbox/{sandboxId}/stop' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY'
curl 'https://app.daytona.io/api/sandbox/{sandboxId}/snapshot' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{ "name": "my-vm-snapshot", "includeMemory": false}'
# A sandbox created from the snapshot starts with the same filesystemcurl 'https://app.daytona.io/api/sandbox' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{"snapshot": "my-vm-snapshot"}'
curl 'https://proxy.app.daytona.io/toolbox/{newSandboxId}/files/download?path=setup.log' \ --header 'Authorization: Bearer YOUR_API_KEY'Lifecycle
Section titled “Lifecycle”Every Linux sandbox moves through a lifecycle. A Linux sandbox can have several different states. Each state reflects the status of your sandbox. A Linux sandbox transitions between states in response to user actions, or automatically when one of its timeouts elapses.
| Feature | Container | Container (ephemeral) | Linux VM | Linux VM (ephemeral) |
|---|---|---|---|---|
| Stop and start | ✓ | ✗ | ✓ | ✗ |
| Pause and resume | ✗ | ✗ | ✓ | ✗ |
| Fork | ✗ | ✗ | ✓ | ✓ |
| Archive | ✓ | ✗ | ✗ | ✗ |
| Delete | ✓ | ✓ | ✓ | ✓ |
| Filesystem persistence | ✓ | ✗ | ✓ | ✗ |
| Memory persistence | ✗ | ✗ | ✓ | ✗ |
| Memory snapshot | ✗ | ✗ | ✓ | ✓ |
| Filesystem snapshot | ✓ | ✗ | ✓ | ✗ |
| Nested virtualization | ✗ | ✗ | ✓ | ✓ |
| Desktop | ✓ VNC | ✓ VNC | ✓ VNC | ✓ VNC |
| State | Description |
|---|---|
| Pending Build | The build is queued. |
| Building Snapshot | The sandbox is building a snapshot from an image. Container sandboxes only. |
| Pulling Snapshot | The sandbox is pulling a snapshot. |
| Creating | The sandbox is being created. |
| Starting | The sandbox is starting. |
| Started | The sandbox is running and accepts requests. |
| Stopping | The sandbox is stopping and does not accept new requests. |
| Stopped | The sandbox is stopped. The filesystem is kept and memory is cleared. |
| Pausing | The Linux VM sandbox is pausing. |
| Paused | The Linux VM sandbox is paused with its filesystem and memory preserved. |
| Resuming | The Linux VM sandbox is resuming from the paused state. |
| Archiving | The container sandbox filesystem is moving to object storage. |
| Archived | The container sandbox filesystem is in object storage. |
| Restoring | The sandbox is being restored. |
| Resizing | The sandbox resources are being changed. |
| Snapshotting | The sandbox is creating a memory snapshot or a filesystem snapshot. |
| Forking | The Linux VM sandbox is being forked. |
| Deleting | The sandbox is being deleted. |
| Deleted | The sandbox is deleted. |
| Error | The sandbox hit an error. A recoverable error can be recovered. |
| Initial state | Target state | Trigger |
|---|---|---|
| Started | Stopping | A stop is requested, or the auto-stop interval elapses. |
| Stopping | Stopped | The shutdown completes. The filesystem is kept and memory is cleared. |
| Stopped | Starting | A start is requested. |
| Started | Pausing | A pause is requested on a Linux VM sandbox, or the auto-pause interval elapses. |
| Pausing | Paused | The filesystem and memory are preserved. |
| Paused | Resuming | A start is requested on a paused Linux VM sandbox. |
| Paused | Stopping | A stop is requested on a paused Linux VM sandbox. |
| Resuming | Started | The sandbox resumes from memory and is running. |
| Stopped | Archiving | An archive is requested on a container sandbox, or the auto-archive interval elapses. |
| Archived | Restoring | A start is requested on an archived container sandbox. |
| Started | Snapshotting | A memory snapshot is requested on a Linux VM sandbox. |
| Stopped | Snapshotting | A filesystem snapshot is requested. |
| Started | Forking | A fork is requested on a Linux VM sandbox. |
| Started | Deleting | A delete is requested, or an ephemeral sandbox is stopped. |
| Stopped | Deleting | A delete is requested, or the auto-delete interval elapses. |
| Deleting | Deleted | The sandbox is removed and its resources are released. |
Wait for state
Section titled “Wait for state”Wait until a sandbox reaches the started or stopped state. Each method takes a timeout in seconds.
sandbox.wait_for_sandbox_start(timeout=60)sandbox.wait_for_sandbox_stop(timeout=60)await sandbox.waitUntilStarted(60)await sandbox.waitUntilStopped(60)sandbox.wait_for_sandbox_start(60)sandbox.wait_for_sandbox_stop(60)err := sandbox.WaitForStart(ctx, 60*time.Second)err = sandbox.WaitForStop(ctx, 60*time.Second)sandbox.waitUntilStarted(60);sandbox.waitUntilStopped(60);Stop / start
Section titled “Stop / start”Stop a sandbox. The sandbox moves to the stopped state when shutdown completes. While a stop is in progress, the sandbox is in the stopping state and does not accept new requests.
Stopping terminates the running container. The filesystem is preserved, but memory state is not. Container sandboxes do not support pause; stop is the way to shut down a container sandbox when it is not in use.
- Go to Daytona Sandboxes ↗
- Click the stop icon (⏹) next to the sandbox you want to stop
sandbox.stop()await sandbox.stop()sandbox.stopsandbox.Stop(ctx)sandbox.stop();daytona stop [SANDBOX_ID] | [SANDBOX_NAME] [flags]curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/stop' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY'Stopping shuts down the virtual machine while preserving the filesystem. Memory state is cleared. To preserve running process state without consuming CPU, use pause / resume.
- Go to Daytona Sandboxes ↗
- Click the stop icon (⏹) next to the sandbox you want to stop
sandbox.stop()await sandbox.stop()sandbox.stopsandbox.Stop(ctx)sandbox.stop();daytona stop [SANDBOX_ID] | [SANDBOX_NAME] [flags]curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/stop' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY'Start a sandbox.
- Go to Daytona Sandboxes ↗
- Click the start icon next to the sandbox you want to start
sandbox.start()await sandbox.start()sandbox.startsandbox.Start(ctx)sandbox.start();daytona start [SANDBOX_ID] | [SANDBOX_NAME] [flags]curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/start' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY'Pause / resume
Section titled “Pause / resume”Pause and resume a sandbox.
Pause is not supported for container sandboxes. The filesystem can be preserved on stop, but memory state is not. Use stop to shut down a container sandbox when it is not in use.
The filesystem and memory state are preserved, and CPU is no longer consumed.
- Ensure the Linux VM sandbox is started
- Pause the Linux VM sandbox
- Wait for the Linux VM sandbox to reach the paused state
- Resume (start) the Linux VM sandbox again when you need to resume it
sandbox.pause()await sandbox.pause()sandbox.pausesandbox.Pause(ctx)sandbox.pause();daytona pause [SANDBOX_ID] | [SANDBOX_NAME]curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/pause' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY'Fork a sandbox.
Forking is not supported for container sandboxes. Use create snapshot from sandbox to capture filesystem state, then create a new sandbox from that snapshot.
Forking creates a duplicate of a Linux VM sandbox’s filesystem and memory state in a new sandbox. The forked sandbox is fully independent: it can be started, stopped, and deleted without affecting the original.
Daytona tracks the parent-child relationship in a fork tree, so you can trace a fork’s lineage back to the sandbox it was created from. You can fork a fork to build branches. The parent sandbox cannot be deleted while it has active fork children.
A fork of a KVM sandbox inherits the kvm setting. Forking a KVM sandbox returns a 403 error if KVM sandboxes are not enabled for your organization.
- Go to Daytona Sandboxes ↗
- Click the three-dot menu (⋮) next to the started Linux VM sandbox you want to fork
- Select
# Fork sandbox through the Sandbox instanceforked = sandbox.fork(name="my-forked-sandbox")// Fork sandbox through the Sandbox instanceconst forkedSandbox = await sandbox.fork({ name: "my-forked-sandbox" });
// Or use the Daytona helper methodconst helperForkedSandbox = await daytona.fork(sandbox, { name: "my-forked-sandbox" });# Fork sandbox through the Sandbox instanceforkedSandbox = sandbox.fork(name: "my-forked-sandbox")// Fork sandbox through the Sandbox instancename := "my-forked-sandbox"forkedSandbox, err := sandbox.Fork(ctx, &name)if err != nil { return err}// Fork sandbox through the Sandbox instanceSandbox forkedSandbox = sandbox.fork("my-forked-sandbox", 60);curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/fork' \ --request POST \ --header 'X-Daytona-Organization-ID: YOUR_ORGANIZATION_ID' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{ "name": "my-forked-sandbox"}'Query fork relationships:
# List direct fork children of a sandboxcurl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/forks' \ --header 'Authorization: Bearer YOUR_API_KEY'
# Get the parent sandbox of a forkcurl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/parent' \ --header 'Authorization: Bearer YOUR_API_KEY'
# Get the full ancestor chain (parent, grandparent, and so on)curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/ancestors' \ --header 'Authorization: Bearer YOUR_API_KEY'Delete
Section titled “Delete”Delete a sandbox.
- Go to Daytona Sandboxes ↗
- Click next to the sandbox you want to delete
sandbox.delete()
# Block until the sandbox is deletedsandbox.delete(timeout=60, wait=True)await sandbox.delete()
// Block until the sandbox is deletedawait sandbox.delete(60, true)sandbox.delete
# Block until the sandbox is deletedsandbox.delete(60, wait: true)err = sandbox.Delete(ctx)
// Block until the sandbox is deletederr = sandbox.DeleteAndWait(ctx, 60*time.Second)sandbox.delete();
// Block until the sandbox is deletedsandbox.delete(60, true);daytona delete [SANDBOX_ID] | [SANDBOX_NAME]curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}' \ --request DELETE \ --header 'Authorization: Bearer YOUR_API_KEY'Timeouts
Section titled “Timeouts”Daytona stops, pauses, archives, or deletes a sandbox when a timeout elapses. Each timeout is set in minutes. Zero disables auto-stop, auto-pause, and wall-clock TTL. Zero does not disable auto-archive or auto-delete: auto-archive set to zero uses the maximum interval of 30 days, and auto-delete set to zero deletes the sandbox as soon as it stops. To disable auto-delete, set it to -1.
| Interval | Container | Linux VM | Action |
|---|---|---|---|
| Auto-stop | ✓ (default 15 minutes) | ✓ | Stops the sandbox after inactivity. |
| Auto-pause | ✗ | ✓ (default 60 minutes) | Pauses the sandbox after inactivity. |
| Auto-archive | ✓ | ✗ | Archives a stopped sandbox. |
| Auto-delete | ✓ | ✓ | Deletes a stopped sandbox. |
| Wall-clock TTL | ✓ | ✓ | Deletes the sandbox at a fixed deadline, in any state. |
Auto-pause
Section titled “Auto-pause”The auto-pause interval sets the amount of time after which an idle VM sandbox is automatically paused. Auto-pause applies only to VM sandboxes and is mutually exclusive with the auto-stop interval: at most one of the two intervals may be non-zero. Ephemeral sandboxes cannot have auto-pause enabled.
The interval is set in minutes:
0: disables the auto-pause functionality- if neither auto-pause nor auto-stop is set, non-ephemeral sandbox classes that support pausing default to an auto-pause interval of 60 minutes with auto-stop disabled
The sandbox pauses after no new events occur for the specified interval. Events include sandbox state changes and interactions with the sandbox through the SDK. Interactions through sandbox previews do not reset the timer.
Auto-pause is not supported for container sandboxes. Use auto-stop to stop a container sandbox after a period of inactivity.
- Go to Daytona Sandboxes ↗
- Click
- Select a Linux VM snapshot
- Set
auto-pauseinterval to the desired value in minutes0: disables the auto-pause functionality- if neither auto-pause nor auto-stop is set, the default interval of 60 minutes is used with auto-stop disabled
- Click
from daytona import CreateSandboxFromSnapshotParams
sandbox = daytona.create(CreateSandboxFromSnapshotParams( snapshot="daytona-vm-small", # Auto-pause after 1 hour of inactivity auto_pause_interval=60,))
# Update the auto-pause interval on an existing sandboxsandbox.set_auto_pause_interval(60)
# Disable auto-pausesandbox.set_auto_pause_interval(0)const sandbox = await daytona.create({ snapshot: 'daytona-vm-small', // Auto-pause after 1 hour of inactivity autoPauseInterval: 60,})
// Update the auto-pause interval on an existing sandboxawait sandbox.setAutoPauseInterval(60)
// Disable auto-pauseawait sandbox.setAutoPauseInterval(0)sandbox = daytona.create( Daytona::CreateSandboxFromSnapshotParams.new( snapshot: 'daytona-vm-small', # Auto-pause after 1 hour of inactivity auto_pause_interval: 60 ))
# Update the auto-pause interval on an existing sandboxsandbox.auto_pause_interval = 60
# Disable auto-pausesandbox.auto_pause_interval = 0// Auto-pause after 1 hour of inactivityautoPauseInterval := 60params := types.SnapshotParams{ Snapshot: "daytona-vm-small", SandboxBaseParams: types.SandboxBaseParams{ AutoPauseInterval: &autoPauseInterval, },}sandbox, err := client.Create(ctx, params)import io.daytona.sdk.Daytona;import io.daytona.sdk.Sandbox;import io.daytona.sdk.model.CreateSandboxFromSnapshotParams;
public class App { public static void main(String[] args) { try (Daytona daytona = new Daytona()) { CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams(); params.setSnapshot("daytona-vm-small"); // Auto-pause after 1 hour of inactivity params.setAutoPauseInterval(60); Sandbox sandbox = daytona.create(params);
// Update the auto-pause interval on an existing sandbox sandbox.setAutoPauseInterval(60);
// Disable auto-pause sandbox.setAutoPauseInterval(0); } }}curl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/autopause/{interval}' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY'Auto-pause is not supported for GPU sandboxes. GPU sandboxes are ephemeral and cannot have auto-pause enabled.
Wall-clock TTL
Section titled “Wall-clock TTL”The wall-clock TTL (time-to-live) sets a hard upper bound on how long a sandbox may exist. Unlike the auto-delete interval, which counts time only while the sandbox is stopped, TTL runs as wall-clock time from creation (or from the moment you last set it) and destroys the sandbox in any state: started, stopped, paused, or archived.
Set ttl_minutes when creating a sandbox, or update it later. The value is in minutes:
0: disables the TTL- if not set, the sandbox has no TTL deadline
Calling set_ttl after creation resets the deadline from the current moment. Use wall-clock TTL for agent sessions, CI jobs, and any sandbox that must not outlive a fixed deadline.
sandbox = daytona.create(CreateSandboxFromSnapshotParams( snapshot="daytona-vm-small", ttl_minutes=120,))
# Reset the deadline to 60 minutes from nowsandbox.set_ttl(60)const sandbox = await daytona.create({ snapshot: 'daytona-vm-small', ttlMinutes: 120,})
// Reset the deadline to 60 minutes from nowawait sandbox.setTtl(60)sandbox = daytona.create( Daytona::CreateSandboxFromSnapshotParams.new( snapshot: 'daytona-vm-small', ttl_minutes: 120 ))
# Reset the deadline to 60 minutes from nowsandbox.ttl_minutes = 60ttlMinutes := 120sandbox, err := client.Create(ctx, types.SnapshotParams{ Snapshot: "daytona-vm-small", SandboxBaseParams: types.SandboxBaseParams{ TtlMinutes: &ttlMinutes, },})CreateSandboxFromSnapshotParams params = new CreateSandboxFromSnapshotParams();params.setSnapshot("daytona-vm-small");params.setTtlMinutes(120);Sandbox sandbox = daytona.create(params);
// Reset the deadline to 60 minutes from nowsandbox.setTtl(60);daytona create --snapshot daytona-vm-small --ttl 120curl 'https://app.daytona.io/api/sandbox' \ --request POST \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' \ --data '{ "snapshot": "daytona-vm-small", "ttlMinutes": 120}'
# Reset the deadline to 60 minutes from nowcurl 'https://app.daytona.io/api/sandbox/{sandboxIdOrName}/ttl/60' \ --request POST \ --header 'Authorization: Bearer YOUR_API_KEY'