vm/skills/bazzite-bootc/SKILL.md
kind:vm entity pairing with the /ov-distros:bazzite bootc container image. source.kind: bootc. Thin pointer skill — composition + layer stack authority lives in /ov-distros:bazzite. This skill documents only the VM-specific fields. MUST be invoked before editing bazzite-bootc in image/bootc/overthink.yml.
npx skillsauth add overthinkos/overthink-plugins bazzite-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:bazzite container image. ov vm build bazzite-bootc runs bootc install to-disk against the bazzite image to produce a bootable qcow2/raw disk.
Composition authority: /ov-distros:bazzite. Layer stack, NVIDIA/CUDA wiring, Kubernetes/Docker tools, desktop apps, OCI labels all live there. This skill is a pointer.
vm:
bazzite-bootc:
source:
kind: bootc
image: bazzite
# disk_size, ram, cpus inherit from VmSpec defaults — override locally if the
# image's workload demands something heavier than 4 GiB / 2 cpus / 20 GiB.
Bazzite's full image definition carries a NVIDIA + CUDA + Kubernetes + Docker stack; for realistic workloads author local overrides (disk_size: 80G, ram: 16G, cpus: 6) before ov vm build.
# Built from the bootc submodule.
ov -C image/bootc image build bazzite
ov -C image/bootc vm build bazzite-bootc --transport containers-storage
ov -C image/bootc vm create bazzite-bootc --ram 16G --cpus 6
ov -C image/bootc vm start bazzite-bootc
See /ov-vm:vm "Known bootc-VM caveats" for the privileged-container -v /dev:/dev loopback requirement and glibc-skew preflight.
/ov-distros:bazzite — composition authority: layer stack, NVIDIA/CUDA wiring, 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 conversiondevelopment
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.