ov-vms/skills/bazzite-ai-bootc/SKILL.md
kind:vm entity pairing with the /ov-foundation:bazzite-ai bootc container image. source.kind: bootc. Thin pointer skill — composition + layer stack authority lives in /ov-foundation:bazzite-ai. This skill documents only the VM-specific fields. MUST be invoked before editing bazzite-ai-bootc in vms.yml.
npx skillsauth add overthinkos/overthink-plugins bazzite-ai-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-foundation:bazzite-ai container image. ov vm build bazzite-ai-bootc runs bootc install to-disk against the bazzite-ai image to produce a bootable qcow2/raw disk.
Composition authority: /ov-foundation:bazzite-ai. Layer stack, NVIDIA/CUDA wiring, Kubernetes/Docker tools, desktop apps, OCI labels all live there. This skill is a pointer.
vms:
bazzite-ai-bootc:
source:
kind: bootc
image: bazzite-ai
# 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-AI'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.
# Enable bazzite-ai in image.yml first (disabled by default)
ov image build bazzite-ai
ov vm build bazzite-ai-bootc
ov vm create bazzite-ai-bootc --ram 16G --cpus 6
ov vm start bazzite-ai-bootc
See /ov-advanced:vm "Known bootc-VM caveats" for the privileged-container -v /dev:/dev loopback requirement and glibc-skew preflight.
/ov-foundation:bazzite-ai — composition authority: layer stack, NVIDIA/CUDA wiring, OCI labels/ov-vms:vms — VmSpec authoring reference, bootc branch authoring recipe/ov-advanced:vm — VM lifecycle commands + bootc-specific caveats/ov-build:migrate — ov migrate vm-spec legacy conversiontools
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).