ov-foundation/skills/bazzite-ai/SKILL.md
Bazzite NVIDIA bootc image with dev tools, CUDA, Kubernetes, Docker, and desktop apps. Currently disabled. Enable in image.yml to build. MUST be invoked before building, deploying, or troubleshooting the bazzite-ai image.
npx skillsauth add overthinkos/overthink-plugins bazzite-aiInstall 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.
Bootc VM image based on Universal Blue's Bazzite (gaming-focused) with NVIDIA drivers, comprehensive dev tools, CUDA, Kubernetes, Docker, and desktop applications.
| Property | Value |
|----------|-------|
| Base | ghcr.io/ublue-os/bazzite-nvidia-open:stable-43.20260120.1 |
| Bootc | true |
| Platforms | linux/amd64 |
| Status | disabled (set enabled: true in image.yml) |
| Registry | ghcr.io/overthinkos |
bazzite-nvidia-open (external bootc base — gaming desktop with NVIDIA)agent-forwarding (gnupg + direnv + ssh-client)build-toolchain, language-runtimes, dev-toolsujust, github-actions, virtualization, kubernetes, docker-cegoogle-cloud, devops-tools, grafana-toolscudadesktop-apps, vscode, typst, copr-desktopvr-streamingos-config, os-system-files/ov-coder:build-toolchain — gcc, cmake, ninja/ov-foundation:cuda — NVIDIA CUDA toolkit/ov-coder:kubernetes-layer — kubectl + Helm/ov-coder:docker-ce — Docker CE + buildx/ov-foundation:vscode — Visual Studio Code/ov-foundation:os-config — Bootc system configuration# Enable in image.yml first (remove enabled: false)
ov image build bazzite-ai
ov vm build bazzite-ai --type qcow2
ov vm create bazzite-ai
ov vm start bazzite-ai
terra-mesa.repo has corrupt zchunk metadata. The generator auto-removes it (rm -f /etc/yum.repos.d/terra-mesa.repo)./ov-foundation:aurora — sibling Universal Blue bootc image with ov toolchain/ov-openclaw:openclaw-browser-bootc — sibling fedora-bootc image/ov-advanced:vm — build and run as a bootc VM/ov-build:build — produce the bootc imageMUST be invoked when the task involves the bazzite-ai bootc image or the Bazzite-based AI workstation VM.
/ov-build:image — image family umbrella (image: entries in overthink.yml, build/validate/inspect/list)tools
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).