Quickstart
Last updated: 2026-06-27
Boot a Linux microVM from an OCI image, run one command inside it, and tear it down. You only need three commands.
1. Install
Section titled “1. Install”brew install geoffbelknap/tap/microagentBuilding from source is covered in Install.
2. Check the host
Section titled “2. Check the host”microagent doctordoctor checks whether this host can boot workspaces and whether the default
kernel is in place. If something is missing, it tells you what to fix. Still
stuck? See Troubleshooting.
3. Boot, run, tear down
Section titled “3. Boot, run, tear down”microagent run docker.io/library/ubuntu:24.04 uname -aThe first argument is the OCI image. Everything after it is the command to run inside the microVM. The first run also downloads the default kernel for this host; later runs reuse it.
Workspace: run-1781164526178302845State: stoppedRootfs: /home/agency/.microagent/workspaces/run-1781164526178302845/rootfs.ext4Profile: smallRestart: neverNetwork: userHostname: run-1781164526178302845Resources: memory=512MiB cpus=2 disk=1024MiBKernel: /home/agency/.microagent/kernels/linux-kvm/amd64/ImageExit code: 0
Linux run-1781164526178302845 6.1.155 #2 SMP PREEMPT_DYNAMIC Sat May 2 18:32:03 UTC 2026 x86_64 x86_64 x86_64 GNU/LinuxIf you run an image without a command, microagent uses the image’s Entrypoint/Cmd.
What just happened
Section titled “What just happened”microagent pulled the Ubuntu image, converted it into an ext4 rootfs, and booted a microVM with its own Linux kernel. The command ran inside the guest. The exit code and output came back to your terminal. Because this was a one-shot run, microagent removed the temporary workspace afterwards.
Related
Section titled “Related”- Run an actual agent inside a microVM - run your first agent.
- Keep a workspace around between runs - persistent workspaces covers
create,start,halt,connect,delete. - Already fluent in Docker? Coming from Docker maps the commands you know.