ov/skills/logs/SKILL.md
Service log viewing for running containers. MUST be invoked before any work involving: ov logs command, viewing container output, or debugging service issues.
npx skillsauth add overthinkos/overthink-plugins logsInstall 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.
Displays logs from a running or recently stopped service container. In quadlet mode, reads from journalctl. In direct mode, reads from the container engine's log store.
| Action | Command | Description |
|--------|---------|-------------|
| View logs | ov logs <image> | Show recent logs |
| Follow logs | ov logs <image> -f | Stream logs in real time |
| Tail N lines | ov logs <image> -n 50 | Show last N lines |
| With instance | ov logs <image> -i 2 | Logs from specific instance |
# View recent logs
ov logs jupyter
# Follow logs in real time (Ctrl+C to stop)
ov logs ollama -f
# Show last 100 lines
ov logs immich -n 100
# Logs from a specific instance
ov logs openclaw -i 2
# Combine follow with tail
ov logs comfyui -f -n 50
| Flag | Description |
|------|-------------|
| -f, --follow | Stream logs continuously |
| -n, --lines LINES | Number of recent lines to show |
| -i, --instance INSTANCE | Target a specific container instance |
journalctl --user -u ov-<image>.service<engine> logs <container>/ov:pull -- Prerequisite: fetch the image into local storage; handles remote refs (@github.com/...) and the ErrImageNotLocal recovery path
/ov:status -- Check service status
/ov:service -- Service lifecycle management
/ov:start -- Starting services
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).