vm/skills/aurora-bootc/SKILL.md
kind:vm entity pairing with the /ov-distros:aurora bootc container image. source.kind: bootc. Thin pointer skill — composition + layer stack authority lives in /ov-distros:aurora. This skill documents only the VM resource sizing. MUST be invoked before editing aurora-bootc in image/bootc/overthink.yml.
npx skillsauth add overthinkos/overthink-plugins aurora-bootcInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
kind: vm entity that pairs with the /ov-distros:aurora container image. ov vm build aurora-bootc runs bootc install to-disk against the aurora image to produce a bootable qcow2/raw disk.
Composition authority: /ov-distros:aurora. Layer stack, base image, tests, and OCI labels all live there. This skill is a pointer; it only documents the VM-specific delta (disk_size / ram / cpus).
vms:
aurora-bootc:
source:
kind: bootc
image: aurora
disk_size: 80 GiB
ram: 12G
cpus: 4
| Setting | Value | Rationale | |---|---|---| | Disk size | 80 GiB | Aurora DX ships full KDE + NVIDIA drivers + toolchain; baseline image footprint is ~30 GiB uncompressed | | RAM | 12G | KDE desktop + NVIDIA stack + ov toolchain working set | | CPUs | 4 | Standard workstation-class dev VM allocation |
Firmware, machine, network, and SSH settings fall back to VmSpec defaults (see /ov-vm:vms-catalog). Override locally in vm.yml if the paired image changes its init system or boot requirements.
# Build the aurora container image first (the VM disk install consumes it)
ov image build aurora # container image must exist before the VM disk install step
ov vm build aurora-bootc
ov vm create aurora-bootc
ov vm start aurora-bootc
ov vm ssh aurora-bootc
See /ov-vm:vm "Known bootc-VM caveats" for the rootful storage split (engine.rootful=sudo needs sudo podman load of the saved tarball to reach root's storage) and the nested-container --transport containers-storage pattern.
/ov-distros:aurora — composition authority: layer stack, base image, OCI labels/ov-vm:vms-catalog — VmSpec authoring reference, bootc branch authoring recipe/ov-vm:vm — VM lifecycle commands + bootc-specific caveats/ov-build:migrate — ov migrate legacy conversion/ov-distros:bootc-base — sshd + qemu-guest-agent + bootc-config bundledevelopment
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.