ov-coder/skills/docker-ce/SKILL.md
Docker CE engine with buildx and compose plugins from the official Docker repository. Use when working with Docker, container builds, or Docker Compose.
npx skillsauth add overthinkos/overthink-plugins docker-ceInstall 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 |
|----------|-------|
| Install files | layer.yml, tasks: |
RPM (from docker-ce-stable repo): containerd.io, docker-buildx-plugin, docker-ce, docker-ce-cli, docker-compose-plugin
rpm: (Fedora — Docker's yum repo), pac: (Arch — docker metapackage from extra), deb: — via distro-version tag sections debian:13: and ubuntu:24.04: because the upstream apt repo URL differs per distro codename (https://download.docker.com/linux/debian trixie vs .../ubuntu noble). Each tag section declares its own repos: block with the correct URL + GPG key; packages (docker-ce, docker-ce-cli, containerd.io, docker-buildx-plugin, docker-compose-plugin) are identical. See /ov-build:layer "distro-version tag sections".
# image.yml
my-image:
layers:
- docker-ce
bazzite-ai (disabled)/ov-foundation:container-nesting — Alternative podman-based nested container support/ov-coder:kubernetes-layer — Sibling kubectl/Helm commonly paired with docker-ce/ov-coder:github-actions — Sibling layer needing a container engine for act runs/ov-build:build — Build the bootc image including docker-ce packages/ov-advanced:vm — Run the bootc image as a VM to test the docker engineUse when the user asks about:
docker-ce layer or Docker repository setup/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).