drover-runner

Unikernel Platform Runner and Hypervisor daemon for executing secure multi-tenant microVM containers.

Part of the Drover parallel orchestration platform.

Key Features

• Local Sandbox Verification: Integrates with local kraft CLI to run unikernel targets offline.
• Firecracker Orchestration: Spawns isolated multi-tenant guest OS slices using Firecracker microVMs on KVM hosts.
• Virtual Isolation: Configures isolated virtual bridge networks (TAP/TUN) and secure overlay disks with dynamic memory cleanup on completion.

Status

🚧 Early development. Foundational components for secure unikernel execution environments.

Backlog & Roadmap

Work items, epics, and tasks are tracked locally in JSON Lines format inside .beads/issues.jsonl following the platform's Beads convention.

See the main drover repository for the coordinator, architecture, and cross-cutting concerns.

Local Development (drun-001)

The fastest way to start hacking on unikernels with drover-runner is via the dvr CLI:

# Build the CLI
go build -o bin/dvr ./cmd/dvr

# See available commands (powered by the official kraft engine)
./bin/dvr --help
./bin/dvr unikernel --help
./bin/dvr unikernel build --help

# Build a unikernel project that contains a Kraftfile
./bin/dvr unikernel build ./path/to/my-unikernel

# Run it locally (QEMU by default)
./bin/dvr unikernel run ./path/to/my-unikernel

See the detailed design and next steps in docs/drun-001-kraft-integration-design.md.

Contributing

This is early-stage infrastructure. Roadmap items are captured in the Beads backlog. Contributions and discussions welcome via issues and PRs once the core daemon stabilizes.