ov-openclaw/skills/openclaw-browser-bootc/SKILL.md
Bootc VM image with OpenClaw gateway, Chrome, VNC, and PipeWire. Currently disabled. Enable in image.yml to build. MUST be invoked before building, deploying, or troubleshooting the openclaw-browser-bootc image.
npx skillsauth add overthinkos/overthink-plugins openclaw-browser-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.
Bootable container (bootc) VM image with OpenClaw AI gateway, Chrome browser, VNC access, and PipeWire audio.
| Property | Value |
|----------|-------|
| Base | quay.io/fedora/fedora-bootc:43 |
| Bootc | true |
| Layers | agent-forwarding, bootc-base, openclaw, pipewire, wayvnc, chrome-sway |
| Platforms | linux/amd64 |
| Ports | 18789 (gateway), 5900 (VNC), 9222 (CDP) |
| Status | disabled (set enabled: true in image.yml) |
| Registry | ghcr.io/overthinkos |
distro: declarationThis image's image.yml entry does not declare distro:. Because base: "quay.io/fedora/fedora-bootc:43" is an external URL (not the name of another image.yml entry), the generator resolves Distro to null, which short-circuits the install_template's Phase-2 branch — no layer rpm: install RUNs are emitted. The image will build cleanly but every layer's declarative rpm: packages are missing; only cmd: dnf install … tasks survive.
This hasn't tripped because the image is enabled: false. Before enabling, add:
openclaw-browser-bootc:
base: "quay.io/fedora/fedora-bootc:43"
bootc: true
distro: ["fedora:43", fedora] # ← add this
...
The same latent bug affects /ov-foundation:bazzite-ai and /ov-foundation:aurora (both external ublue bases). See /ov-build:image "External Bases Require Explicit distro:" for the full mechanism; /ov-selkies:selkies-desktop-bootc is the canonical working reference.
| Setting | Value | |---------|-------| | SSH port | 2222 | | Disk size | 20 GiB | | RAM | 4G | | CPUs | 2 |
fedora-bootc:43 (external bootc base)bootc-base — sshd + guest agent + bootc configopenclaw — AI gatewaypipewire — audio serverwayvnc — VNC serverchrome-sway — Chrome in Sway compositor| Port | Service | Protocol | |------|---------|----------| | 18789 | OpenClaw gateway | HTTP | | 5900 | VNC | TCP | | 9222 | Chrome DevTools | HTTP |
# Enable in image.yml first (remove enabled: false)
ov image build openclaw-browser-bootc
ov vm build openclaw-browser-bootc --type qcow2
ov vm create openclaw-browser-bootc --ram 4G --cpus 2
ov vm start openclaw-browser-bootc
ov vm ssh openclaw-browser-bootc -p 2222
/ov-foundation:bootc-base — SSH + guest agent/ov-openclaw:openclaw — AI gateway/ov-selkies:chrome-sway — Chrome in Sway/ov-openclaw:openclaw-sway-browser — container variant (enabled)/ov-openclaw:openclaw-ollama-sway-browser — with Ollama LLM (enabled)/ov-selkies:selkies-desktop-bootc — sibling bootc image with distro: correctly declared; follow its pattern when enabling this one/ov-foundation:bazzite-ai, /ov-foundation:aurora — share the same latent distro: bug/ov-build:image — external-base distro: requirement explanation/ov-advanced:vm — VM lifecycle, /dev:/dev mount, vm.ssh_port plumbing, bootc-VM caveats/ov-foundation:bootc-base — the bootc composition layer pulled in first/ov-foundation:bootc-config — bootc boot wiring (tty1 autologin, graphical target, systemd-user supervisord)MUST be invoked when the task involves the openclaw-browser-bootc VM image or bootc-based OpenClaw deployment.
/ov-build:build — build.yml vocabulary (distros, builders, init-systems)development
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.