infrastructure/skills/gocryptfs/SKILL.md
Encrypted filesystem (gocryptfs) for charly config encrypted volume operations. Use when working with encrypted volumes, charly config mount/unmount, or filesystem encryption.
npx skillsauth add overthinkos/overthink-plugins gocryptfsInstall 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 | charly.yml (packages only) |
RPM: gocryptfs
rpm: (Fedora), pac: (Arch — community), deb: (Debian/Ubuntu — gocryptfs available in Debian main) — full parity.
# charly.yml
my-image:
candy:
- gocryptfs
Typically used as part of the charly candy (the full toolchain: charly binary + virtualization + gocryptfs + socat) rather than directly.
When charly config mount or charly start mounts encrypted volumes, each gocryptfs daemon runs inside a systemd-run --scope --user --unit=charly-enc-<image>-<volume> scope unit. This decouples the FUSE mount lifecycle from the container service — mounts survive container stop/restart and remain browsable on the host.
The -allow_other flag is always passed to gocryptfs (required for rootless podman with --userns=keep-id). gocryptfs auto-enables default_permissions, so kernel UNIX permission checks still apply.
See /charly-automation:enc for full encrypted volume operations documentation.
charly candy's full toolchain (used in githubrunner)/charly-infrastructure:virtualization -- part of the charly candy alongside gocryptfs/charly-infrastructure:socat -- part of the charly candy alongside gocryptfsUse when the user asks about:
charly config encrypted volume operations (mount, unmount, status, passwd)gocryptfs candycharly-enc-*)/charly-image:layer — candy authoring reference (tasks, vars, env_provide, tests block syntax)/charly-check:check — declarative testing framework for the check: blocktools
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).