Logs

Every sandbox records captured output to disk so you can read it later, even after the sandbox stops or crashes. Use msb logs <name> from the CLI or logs() from the SDK.

Read logs

msb logs devbox
msb logs devbox --tail 100
msb logs devbox -f
msb logs devbox --grep ERROR
msb logs devbox --json | jq 'select(.s == "stderr")'

The default output includes user-program stdout, stderr, and PTY output. Add system diagnostics when you need runtime or kernel logs:

msb logs devbox --source system
msb logs devbox --source all

Read from the SDK

let handle = Sandbox::get("web").await?;
let entries = handle.logs(&LogOptions::default())?;

const handle = await Sandbox.get("web");
const entries = await handle.logs();

handle = await Sandbox.get("web")
entries = await handle.logs()

handle, err := m.GetSandbox(ctx, "web")
entries, err := handle.Logs(ctx, m.LogOptions{})

Use log options to filter at read time:

let recent = handle.logs(&LogOptions {
    tail: Some(50),
    sources: vec![LogSource::Stdout, LogSource::Stderr],
    ..Default::default()
})?;

const recent = await handle.logs({
    tail: 50,
    sources: ["stdout", "stderr"],
});

recent = await handle.logs(tail=50, sources=["stdout", "stderr"])

recent, err := handle.Logs(ctx, m.LogOptions{
    Tail: 50,
    Sources: []m.LogSource{m.LogSourceStdout, m.LogSourceStderr},
})

Sources

Source	Meaning
`stdout`	Captured from a non-interactive session’s stdout
`stderr`	Captured from a non-interactive session’s stderr
`output`	Captured from a PTY session, where stdout and stderr are merged
`system`	Lifecycle markers plus runtime and kernel diagnostics

Interactive sessions use a PTY, so stdout and stderr are merged before microsandbox receives them. Non-interactive exec calls keep the streams separate.

Diagnostic flows

Sandbox crashed

msb ls
msb logs <name>
msb logs <name> --source system

Sandbox will not start

msb create --name nope ...
msb logs nope --source system

Program produced no logs msb create only boots a sandbox. Run something with msb run, msb exec, or an SDK exec call to produce user-program output.

On disk

Sandbox logs live under <sandbox-dir>/logs/:

File	Contents
`exec.log`	User-program output as JSON Lines
`runtime.log`	Sandbox runtime diagnostics
`kernel.log`	Guest kernel and agent console output
`boot-error.json`	Structured startup failure details, when boot fails early

Getting Started

Sandboxes

Networking

Observability

Images

Troubleshooting

Read logs

Read from the SDK

Sources

Diagnostic flows

On disk

​Read logs

​Read from the SDK

​Sources

​Diagnostic flows

​On disk

Read logs

Read from the SDK

Sources

Diagnostic flows

On disk