Console
The console is the human debugging path into a running microVM. Use it when you need a terminal, a shell prompt, or a one-off command with terminal semantics.
Programmatic automation should usually use mvmctl exec, mvmctl proc, or
the SDK runtime surface instead. Those paths are easier to script, test, and
audit.
Security model
Section titled “Security model”Console access is intentionally gated by the image mode. Development images can expose a console; sealed production images should refuse interactive shell access and rely on declared entrypoints, logs, guest RPC, and audit records.
That distinction matters because an interactive shell is broad authority inside the guest. It is useful for debugging, but it is not the default control plane for production workloads.
Common commands
Section titled “Common commands”mvmctl up ./my-app --name devboxmvmctl console devboxmvmctl console devbox --command "uname -a"Use --command for a one-shot shell command when you want console transport
but not an interactive session. Use mvmctl exec for normal automation.
When to use which surface
Section titled “When to use which surface”| Need | Prefer |
|---|---|
| Human debugging | mvmctl console <name> |
| Scripted command execution | mvmctl exec <name> -- <cmd> |
| Process lifecycle control | mvmctl proc start/list/wait/kill |
| File transfer | mvmctl fs or mvmctl cp |
| Service logs | mvmctl logs <name> |