ov-foundation/skills/dbus/SKILL.md
D-Bus session bus for inter-process communication inside containers. Use when working with D-Bus, desktop services, Wayland compositor dependencies, or ov eval dbus commands.
npx skillsauth add overthinkos/overthink-plugins dbusInstall 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.
| Property | Value |
|----------|-------|
| Dependencies | supervisord |
| Service | dbus (supervisord, priority 2) |
| Install files | tasks: |
| Variable | Value |
|----------|-------|
| DBUS_SESSION_BUS_ADDRESS | unix:path=/tmp/dbus-session |
dbus-daemon (RPM)RPM: dbus-daemon (Fedora) · PAC: dbus (Arch) · DEB: dbus (Debian/Ubuntu). Full parity — same DBUS_SESSION_BUS_ADDRESS env, same supervisord fragment, identical behavior downstream.
# image.yml -- now included in all images with supervisord
my-image:
layers:
- dbus
ov eval dbus IntegrationThe ov eval dbus command provides native Go D-Bus interaction with containers via godbus/dbus/v5. It operates in two modes:
ov eval dbus notify myimage "title" "body"): delegates to the container's ov binary via engine exec container ov eval dbus notify . "title" "body". Falls back to gdbus call if ov binary is not in the container.ov eval dbus notify . "title" "body"): connects directly to the local session bus. This is what runs inside the container when delegated from the host.ov eval dbus notify <image> "title" "body" # Send desktop notification
ov eval dbus list <image> # List D-Bus services
ov eval dbus call <image> <dest> <path> <method> [type:value...] # Generic method call
ov eval dbus introspect <image> <dest> <path> # Service introspection
ov cmd/ov tmux cmd/ov eval record cmd → sendContainerNotification() → ov eval dbus notify → org.freedesktop.Notifications.Notify → swaync/mako → desktop popup
For notifications to work, the image needs:
dbus layer — D-Bus session bus (this layer)swaync layer — notification daemonov layer — in-container ov binary for native D-Bus (falls back to gdbus from glib2)ov eval dbus provides explanatory errors when D-Bus is unavailable:
dbus layerswayncov binary → falls back to gdbus, warns about adding ov layerov status ProbeThe dbus probe checks:
dbus-daemon process is runningShows as dbus:ok (notify:swaync) in ov status detail view.
sway in all desktop images/ov-foundation:supervisord -- process manager dependency/ov-selkies:sway -- primary consumer (Sway depends on dbus)/ov-selkies:swaync -- notification daemon (depends on dbus)/ov-selkies:libnotify -- notify-send CLI tool (depends on dbus)/ov-foundation:ov -- in-container ov binary for native D-Bus/ov-advanced:dbus — Native Go D-Bus commands (notify, list, call, introspect)Use when the user asks about:
DBUS_SESSION_BUS_ADDRESS environment variableov eval dbus commands (notify, call, list, introspect)/ov-build:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov-build:eval — declarative testing (eval: block, ov eval image, ov eval live)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).