coder/skills/ubuntu-coder/SKILL.md
Kitchen-sink development box on Ubuntu 24.04 noble: coding + AI-coding CLIs + DevOps tooling in one container. Ubuntu base, 30+ direct candies mirroring fedora-coder's stack. Runs as uid 1000 `ubuntu` — the upstream ubuntu:24.04 account, adopted verbatim via the embedded build vocabulary's base_user declaration. 142/0/1-skip tests pass. Use when working with the ubuntu-coder box — especially when the `${USER}` / `${HOME}` / sudoers differ from the other three coder boxes.
npx skillsauth add overthinkos/overthink-plugins ubuntu-coderInstall 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.
Ubuntu 24.04 noble counterpart of /charly-coder:fedora-coder. Same 80-line test block, same ~30 candies, same rootless posture — but the resolved user is ubuntu (not user) because the upstream ubuntu:24.04 base image ships a pre-existing ubuntu:ubuntu account at uid 1000, and the embedded distro.ubuntu vocabulary declares base_user: to adopt it. Everything that touches the user account — ${HOME}, npm prefix, pixi env, sudoers — derives from resolved.User = "ubuntu".
Location: lives in the
overthinkos/ubunturepo (git submodule atbox/ubuntu) — a SEPARATE repo fromoverthinkos/debian. Its ~31 candies are pulled by github reference from the main repo. Build/validate from the submodule:charly -C box/ubuntu box build ubuntu-coder, orcharly --repo overthinkos/ubuntu box build ubuntu-coder. Deploy-mode verbs read the built image's OCI labels and work from anywhere once it's local.
ubuntu-coder:
base: ubuntu
ports:
- "2222:2222" # sshd-wrapper
- "18765:18765" # charly-mcp (Streamable HTTP)
candy:
# Same stack as debian-coder — see that skill for the full list
- agent-forwarding
- sshd
- charly
- charly-mcp
- container-nesting
- dbus
- tmux
- language-runtimes
- golang
- nodejs
- rust
- pixi
- uv
- build-toolchain
- dev-tools
- pre-commit
- direnv
- gh
- typst
- asciinema
- claude-code
- codex
- gemini
- forgecode
- oracle
- devops-tools
- kubernetes
- docker-ce
- github-actions
- google-cloud
- google-cloud-npm
- grafana-tools
The embedded build vocabulary (charly/charly.yml) declares distro.ubuntu.base_user:
base_user:
name: ubuntu
uid: 1000
gid: 1000
home: /home/ubuntu
ubuntu-coder doesn't set an explicit user: field, so user_policy: auto (the default) adopts the base_user. The generator emits no useradd — the bootstrap section is a one-line comment:
# User ubuntu (uid=1000) adopted from base image (declared in the embedded distro.base_user) — no useradd needed
WORKDIR /home/ubuntu
USER 1000
Resolved identity: User=ubuntu, UID=1000, GID=1000, Home=/home/ubuntu. The image's OCI labels carry these values (ai.opencharly.user="ubuntu", ai.opencharly.home="/home/ubuntu") so deploy-mode quadlets and charly shell find them without re-reading charly.yml.
Why adopt over rename? Ubuntu's cloud-init tooling, documentation, and /etc/passwd metadata all expect the user to be named ubuntu. Renaming fights the upstream contract. Adopting honors it. See /charly-image:image "user_policy" for the full rationale and the 3-value policy table.
$ charly shell ubuntu-coder -c 'id; /usr/bin/dotnet --version; sudo -l'
uid=1000(ubuntu) gid=1000(ubuntu) groups=1000(ubuntu),4(adm),20(dialout),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),105(libvirt)
9.0.313
User ubuntu may run the following commands on <host>:
(ALL : ALL) ALL
Identical to /charly-coder:debian-coder — the only diff is User field.
| Field | Value | Source |
|---|---|---|
| cap_add | (empty) | — |
| security_opt | [unmask=/proc/*] | /charly-distros:container-nesting |
| devices | [/dev/fuse, /dev/net/tun] | /charly-distros:container-nesting |
| privileged | false | — |
| Network | bridge | defaults |
| UID / user | 1000 / ubuntu | adopt mode |
| sudo | passwordless via /etc/sudoers.d/charly-user (discovered via getent passwd 1000 → ubuntu) | /charly-coder:sshd |
exclude_distros: [ubuntu:24.04] (/charly-coder:dev-tools). Ubuntu 24.04 noble main does not ship fastfetch (Debian 13 trixie does, and so do Fedora/Arch). Skipping is cleaner than failing — see /charly-check:check for the exclude_distros: field of the declarative-test schema.dotnet-install.sh (same as debian-coder). Note: Canonical's noble main/universe ships dotnet-sdk-8.0 and dotnet-sdk-10.0 but NOT 9.0; Microsoft's noble apt repo ships 10.0 only. dotnet-install.sh --channel 9.0 is the only cross-distro-consistent path to .NET 9. See /charly-coder:language-runtimes.getent discovery, bat→batcat symlink, virtualization package-existence tests — all are implemented once in the respective candies and work uniformly on both debian-coder and ubuntu-coder.charly check box ghcr.io/overthinkos/ubuntu-coder:latest — 142 passed · 0 failed · 1 skipped (fastfetch, by design).
# 1. Validate
charly -C box/ubuntu box validate
# 2. Build (auto-chains: ubuntu → ubuntu-builder → ubuntu-coder)
charly -C box/ubuntu box build ubuntu-coder
# 3. Disposable-container tests
charly check box ghcr.io/overthinkos/ubuntu-coder:latest
# 4. Confirm adopt mode at runtime
charly shell ubuntu-coder -c "id"
# → uid=1000(ubuntu) gid=1000(ubuntu) ...
# 5. Deploy + live tests
charly config ubuntu-coder
charly start ubuntu-coder
charly check box ghcr.io/overthinkos/ubuntu-coder:latest
Rebuilding the ubuntu base image pulls from docker.io/library/ubuntu:24.04. Unauthenticated Dockerhub pulls are rate-limited (100/6h per IP). If the build fails with toomanyrequests, the cleanest workaround is to pull from a non-Dockerhub mirror and retag:
podman pull public.ecr.aws/docker/library/ubuntu:24.04
podman tag public.ecr.aws/docker/library/ubuntu:24.04 docker.io/library/ubuntu:24.04
charly box build ubuntu-coder
AWS ECR Public mirrors the Dockerhub library namespace without rate-limiting unauthenticated pulls.
| Port | Service | Bound by |
|---|---|---|
| 2222 | sshd-wrapper (SSH as ubuntu with sudo) | /charly-coder:sshd |
| 18765 | charly-mcp | /charly-coder:charly-mcp |
Conflicts with the other three coder-family boxes on these ports.
~10.2 GB uncompressed, nearly identical to /charly-coder:debian-coder.
/charly-coder:fedora-coder — RPM-family, user:user create./charly-coder:arch-coder — pacman-family + AUR, user:user create./charly-coder:debian-coder — deb on Debian 13, user:user create./charly-coder:ubuntu-coder — this box; deb on Ubuntu 24.04, user:ubuntu adopt./charly-distros:ubuntu — parent base; declares base_user: in the embedded build vocabulary./charly-distros:ubuntu-builder — multi-stage builder, also runs as ubuntu:1000./charly-coder:sshd — getent-based sudoers (works regardless of whether the uid-1000 account is user or ubuntu)./charly-coder:dev-tools — bat→batcat + fastfetch exclude_distros./charly-coder:language-runtimes — Microsoft dotnet-install.sh for .NET 9./charly-infrastructure:virtualization — package: + package_map: tests./charly-distros:container-nesting, /charly-tools:charly, /charly-coder:charly-mcp — shared rootless baseline./charly-image:image — user_policy: field (the pivot for this box's behavior)./charly-build:build — base_user: declaration (where ubuntu:1000 is declared)./charly-check:check — exclude_distros: field reference./charly-build:generate — adopt-vs-create writeBootstrap emission./charly-core:shell, /charly-core:charly-config, /charly-core:start, /charly-core:stop.MUST be invoked when:
ubuntu-coder.${USER} or ${HOME} inside an Ubuntu container (they resolve to ubuntu / /home/ubuntu, not user / /home/user).user; use getent passwd 1000 or ${USER} substitution in task fields where the generator expands it.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).