overthinkos/fedora-charly
distros/skills/fedora-ov/SKILL.md
Fedora image with the full charly toolchain using shared layers. Rootless-first — runs as uid=1000 with passwordless sudo (no root, no cap_add: ALL). Same layer list as arch-ov. Includes NVIDIA GPU runtime. MUST be invoked before building, deploying, configuring, or troubleshooting the fedora-charly image.
tools
Updated Jun 9, 2026
$ install --global
skillsauthnpx skillsauth add overthinkos/overthink-plugins fedora-charlyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 9, 2026, 6:42 AM149.9s1 file scanned
SKILL.md
- name:
- fedora-charly
- description:
- |
- runs as uid=1000 with passwordless sudo (no root, no cap_add:
- ALL). Same layer
fedora-charly
Fedora container with the full charly toolchain. Uses almost the same
layer list as /charly-coder:arch-ov — the tag system handles
Fedora-specific packages and scripts via rpm: sections. Supports
nested containers at any depth via /charly-distros:container-nesting.
Lives in the overthinkos/fedora repo (git submodule at image/fedora).
Its fedora base comes from the main repo's base.yml, reached as ov.fedora
via the submodule's import: of the main repo under the ov namespace; its
layers (incl. the nvidia layer) are pulled by github reference. Build from the
submodule: charly -C image/fedora image build fedora-ov. Deploy-mode verbs work
from anywhere once the image is in local storage.
Image Properties
| Property | Value |
|----------|-------|
| Base | fedora (quay.io/fedora/fedora:43) |
| Tags | [all, rpm, fedora, fedora:43] |
| Layers | agent-forwarding, ov, golang, gh, sshd, container-nesting, nvidia |
| Platforms | linux/amd64 |
| UID / user | 1000 / user (rootless-first) |
| Network | host |
| Security | layer-level only (from /charly-distros:container-nesting) |
| Registry | ghcr.io/overthinkos |
Rootless-first posture
Runs as uid=1000 / user with no added capabilities. The
/charly-distros:container-nesting kernel RCA establishes that
unmask=/proc/* + subuid/subgid delegation is sufficient for rootless
nested containers + rootless libvirt VMs, so this image — like its
power-user siblings (/charly-coder:arch-ov, /charly-coder:fedora-coder,
/charly-distros:githubrunner) — needs no cap_add: [ALL] or
label=disable / seccomp=unconfined.
The /charly-coder:sshd layer installs /etc/sudoers.d/charly-user with
passwordless sudo for user, so anything that genuinely needs root
is one sudo prefix away. Default user for every process is uid=1000.
Resolved OCI security label:
| Field | Value |
|---|---|
| cap_add | (empty) |
| security_opt | [unmask=/proc/*] (from /charly-distros:container-nesting) |
| devices | [/dev/fuse, /dev/net/tun] (from /charly-distros:container-nesting) |
| privileged | false |
See /charly-openclaw:openclaw-desktop (streaming-desktop sibling) and
/charly-coder:fedora-coder (kitchen-sink dev sibling) for other images
sharing this posture, and /charly-distros:container-nesting for the
kernel mount_too_revealing() RCA.
Why still network: host
fedora-ov uses host networking (unlike arch-ov, which uses bridge)
so the image can reach host services and the host namespace directly.
charly-mcp's rewriteMCPURLForHost handles host-networked containers via
HostConfig.NetworkMode=host detection (see
ov/mcp_client.go:lookupHostPort), so host networking does not break
MCP URL rewriting. If you want charly-mcp on fedora-ov, compose it
into the layer list — it will work on either networking mode.
What's Installed
Full charly toolchain via shared layers:
- ov — the full toolchain: charly binary + VM tools (qemu-kvm, qemu-img, libvirt tools) + gocryptfs + socat + gvisor-tap-vsock + podman-machine
- golang — Go compiler (
golang-bin) - gh — GitHub CLI +
git+git-lfs(single-responsibility; see/charly-coder:gh) - sshd — SSH server/client (
openssh-server,openssh-clients) + passwordless sudo foruser - container-nesting — buildah, fuse-overlayfs, shadow-utils, skopeo, tailscale, libsecret + nested container config (Tailscale from
tailscale-stablerepo) - nvidia — nvidia-container-toolkit, libva-nvidia-driver (from negativo17 repo; driver libs provided by CDI at runtime)
Lifecycle
# Build (from the overthinkos/fedora submodule)
charly -C image/fedora image build fedora-charly
# Interactive shell (as uid=1000)
charly shell fedora-charly
# Run a command
charly shell fedora-charly -c "charly version"
charly shell fedora-charly -c "sudo -n whoami" # root (passwordless)
# Start as service
charly start fedora-charly
charly status fedora-charly
charly stop fedora-charly
Nested Containers
Rootless podman works inside fedora-charly at any nesting depth. The
/charly-distros:container-nesting layer provides the config + env vars +
subuid/subgid delegation per the podman/stable recipe:
# Level 1: run containers inside fedora-charly
charly shell fedora-charly -c "podman run --rm quay.io/libpod/alpine:latest echo hello"
# Level 2: run charly inside fedora-charly inside fedora-charly
charly shell fedora-charly -c "charly shell fedora-charly -c 'charly version'"
Use quay.io/libpod/alpine:latest instead of
docker.io/library/alpine to dodge Docker Hub rate limits.
GPU Support
The /charly-distros:nvidia layer provides NVIDIA GPU runtime:
nvidia-container-toolkit— CDI spec generation (driver userspace libs provided by CDI at runtime, matching host kernel module)libva-nvidia-driver— VA-API acceleration
charly automatically calls EnsureCDI() before launching GPU
containers. GPU access works at any nesting depth.
Verification
charly shell fedora-charly -c "id" # uid=1000(user)
charly shell fedora-charly -c "sudo -n whoami" # root
charly shell fedora-charly -c "charly version"
charly shell fedora-charly -c "charly doctor"
charly shell fedora-charly -c "podman info"
charly shell fedora-charly -c "podman run --rm quay.io/libpod/alpine:latest echo OK"
charly shell fedora-charly -c "which nvidia-ctk"
# Verify OCI tags
charly box inspect fedora-charly --format tags
# ["all","rpm","fedora","fedora:43"]
Unified with arch-charly
Both fedora-ov and /charly-coder:arch-ov use the exact same layer
list. The tag system (build: [rpm] + distro: ["fedora:43", fedora]
vs build: [pac] + distro: [arch]) selects the right packages
and scripts per distro.
Key Layers
/charly-tools:charly— the full toolchain: charly binary plus VM/encryption tools/charly-distros:container-nesting— nested rootless podman/buildah (authoritative RCA formount_too_revealing()+unmask=/proc/*)/charly-coder:sshd— SSH daemon + passwordless sudo foruser/charly-coder:gh— GitHub CLI + git + git-lfs (owns all git tooling)/charly-distros:nvidia— NVIDIA GPU runtime
Related Images
/charly-distros:fedora— parent base image/charly-coder:arch-ov— Arch counterpart, same layers, same rootless posture/charly-coder:fedora-coder— kitchen-sink dev sibling (32 layers, adds coding CLIs + DevOps)/charly-openclaw:openclaw-desktop— streaming-desktop counterpart (charly toolchain + browser-accessible Wayland); shares the rootless-first posture/charly-distros:githubrunner— self-hosted GitHub Actions runner; same uid=1000 posture
Related Commands
/charly-core:shell— open an interactive shell in fedora-charly (as uid=1000 with sudo)/charly-core:service— manage fedora-charly as a service/charly-vm:vm— nested libvirt VMs viaqemu:///session(rootless)/charly-build:charly-mcp-cmd— MCP gateway deployment patterns (if you addcharly-mcpto the layers)
Related
/charly-image:image— image family umbrella (image:entries incharly.yml, build/validate/inspect/list)/charly-build:build—build.ymlvocabulary (distros, builders, init-systems)
Related Skills
overthinkos/plugin
tools
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Jun 22, 2026
overthinkos/cue
tools
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Jun 16, 2026
overthinkos/egress
tools
VerifiedTrustedCommunity
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).
SKILL.mdUpdated Jun 16, 2026
overthinkos/check-k8s
tools
VerifiedTrustedCommunity
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).
SKILL.mdUpdated Jun 14, 2026