distros/skills/ubuntu/SKILL.md
Base Ubuntu 24.04 noble image. Root of the image hierarchy for Ubuntu- based builds. Runs as uid 1000 `ubuntu` via ADOPT mode — the upstream ubuntu:24.04 base image ships a pre-existing ubuntu:ubuntu account, and build.yml distro.ubuntu declares base_user to adopt it verbatim. MUST be invoked before building, deploying, configuring, or troubleshooting any Ubuntu-based image.
npx skillsauth add overthinkos/overthink-plugins ubuntuInstall 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.
Base Ubuntu 24.04 (noble) image. Distinguished from /ov-distros:debian by adopt mode: the upstream ubuntu:24.04 base image ships a pre-existing ubuntu:ubuntu account at uid 1000, and build.yml distro.ubuntu declares base_user: so the ov generator honors that account rather than creating a new one.
The Ubuntu family lives in its own overthinkos/ubuntu repo (git submodule
at image/ubuntu) — a SEPARATE repo from overthinkos/debian (Debian and
Ubuntu each have their own repo). The ubuntu base is owned there and
composes the main repo's layers + shared build.yml by git reference. Because
distro.ubuntu is inherits: debian, the single remote build.yml (which
carries BOTH distro configs) resolves the inheritance — overthinkos/ubuntu
needs no reference to overthinkos/debian. Build from the submodule:
ov -C image/ubuntu image build ubuntu (or ov --repo overthinkos/ubuntu image build ubuntu).
Nothing in main consumes any Ubuntu image, so there is no main ↔ ubuntu coupling.
| Property | Value |
|----------|-------|
| Base | ubuntu:24.04 |
| Pkg | deb |
| Distro tags | ["ubuntu:24.04", "ubuntu", "debian"] (falls back to debian for package resolution) |
| Layers | (none — base image only) |
| Platforms | linux/amd64 |
| User | ubuntu / uid 1000 (adopt mode) |
| Home | /home/ubuntu |
| Registry | ghcr.io/overthinkos |
build.yml distro.ubuntu inherits from distro.debian (same apt bootstrap template) and adds a base_user: block:
distro:
ubuntu:
inherits: debian
base_user:
name: ubuntu
uid: 1000
gid: 1000
home: /home/ubuntu
Any downstream image with user_policy: auto (the default) that did not explicitly set its own user: field will adopt this — resolved.User = "ubuntu", resolved.Home = "/home/ubuntu", resolved.UserAdopted = true. The bootstrap emits no useradd; it emits a one-line comment documenting the adoption:
# User ubuntu (uid=1000) adopted from base image (declared in build.yml distro.base_user) — no useradd needed
WORKDIR /home/ubuntu
USER 1000
This architecture is declarative (what the base image ships) + policy-driven (how to reconcile with the image's configured user). Three policy values:
| Policy | Behavior on this base |
|--------|----------------------|
| auto (default) | Adopt ubuntu:ubuntu — image inherits the upstream account. |
| adopt | Same as auto here; hard-errors on bases without base_user:. |
| create | Override — force-create a different uid-1000 account (fails if useradd collides). |
See /ov-image:image "user_policy" and /ov-build:build "base_user" for the full table covering all four distros.
Adopt mode honors the existing ubuntu account rather than renaming it to user via usermod -l, because:
/etc/passwd metadata assume the account is named ubuntu.Adopt mode respects the base image's contract and scales declaratively. See /ov-coder:sshd for the getent passwd 1000 pattern that makes layer content (sudoers in particular) work uniformly across both create and adopt modes.
FROM ubuntu:24.04
RUN --mount=type=cache,dst=/var/cache/apt,sharing=locked
--mount=type=cache,dst=/var/lib/apt,sharing=locked
apt-get update && apt-get install -y --no-install-recommends curl ca-certificates gnupg && \
... install go-task binary ...
# User ubuntu (uid=1000) adopted from base image (declared in build.yml distro.base_user) — no useradd needed
WORKDIR /home/ubuntu
USER 1000
The upstream ubuntu:24.04 pull from Dockerhub is unauthenticated-rate-limited (100 pulls / 6h / IP). If ov image build ubuntu fails with toomanyrequests, pull from AWS ECR Public 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
ov image build ubuntu
ECR Public mirrors the Dockerhub library namespace without rate-limiting.
/ov-distros:ubuntu-builder — pixi/npm/cargo multi-stage builder./ov-coder:ubuntu-coder — kitchen-sink dev image./ov-distros:ubuntu-debootstrap-builder — privileged debootstrap builder (base: debian:13)./ov-distros:ubuntu-debootstrap — bootstrap-from-scratch rootfs./ov-vm:ubuntu — the ubuntu-debootstrap bootstrap VM + eval-ubuntu-debootstrap-vm bed.ov -C image/ubuntu image build ubuntu
ov shell ubuntu # drops into /home/ubuntu as uid 1000
id # uid=1000(ubuntu) gid=1000(ubuntu)
ov -C image/ubuntu image validate # remote build.yml resolves distro.ubuntu (inherits debian)
/ov-distros:debian — sibling deb-family base without adopt mode (Debian 13 ships no pre-existing uid-1000 user)./ov-distros:ubuntu-builder — multi-stage builder./ov-coder:ubuntu-coder — kitchen-sink dev image./ov-distros:fedora — RPM-family counterpart./ov-distros:arch — pacman-family counterpart./ov-build:build — base_user: declaration format, which lives in build.yml distro.ubuntu./ov-image:image — user_policy: field + reconciliation./ov-build:generate — adopt-vs-create writeBootstrap emission./ov-coder:sshd — getent passwd 1000-based sudoers works for both user (create) and ubuntu (adopt)./ov-coder:language-runtimes — Microsoft dotnet-install.sh (Ubuntu noble doesn't ship dotnet-sdk-9.0 in main; Microsoft's noble apt repo only has 10.0; the dotnet-install.sh --channel 9.0 is the cross-distro solution).MUST be invoked when:
ubuntu base image.ubuntu:ubuntu identity by default).${USER} / ${HOME} differences between Ubuntu and other deb-based images (ubuntu-coder → ubuntu:/home/ubuntu; debian-coder → user:/home/user)./etc/sudoers.d/ov-user says ubuntu ALL=(ALL) NOPASSWD: ALL rather than user.development
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.