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
box: 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 box 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 bundletools
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
tools
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
tools
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
tools
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).