overthinkos/ubuntu-builder
ov-foundation/skills/ubuntu-builder/SKILL.md
Minimal Ubuntu 24.04 builder image (pixi + Node.js + build-toolchain) used as the multi-stage builder for Ubuntu-based images — currently ubuntu-coder. Runs as uid 1000 `ubuntu` (adopted from the upstream ubuntu:24.04 base image via build.yml's base_user declaration). MUST be invoked before building, deploying, configuring, or troubleshooting the ubuntu-builder image.
tools
Updated May 4, 2026
$ install --global
skillsauthnpx skillsauth add overthinkos/overthink-plugins ubuntu-builderInstall 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: May 4, 2026, 6:26 AM281.3s1 file scanned
SKILL.md
- name:
- ubuntu-builder
- description:
- |
- ubuntu:
- 24.04 base image via build.yml's base_user declaration).
ubuntu-builder
Ubuntu 24.04 (noble) counterpart of /ov-foundation:fedora-builder and /ov-foundation:debian-builder. Same role — pixi/npm/cargo multi-stage builder — with one important difference: the builder runs as ubuntu (uid 1000) because the upstream ubuntu:24.04 base image ships a pre-existing ubuntu:ubuntu account at uid 1000, and build.yml distro.ubuntu.base_user adopts it.
Image Properties
| Property | Value |
|----------|-------|
| Base | ubuntu (which = ubuntu:24.04 + our bootstrap) |
| Layers | pixi, nodejs, build-toolchain |
| Platforms | linux/amd64 |
| Registry | ghcr.io/overthinkos |
| User | ubuntu / uid 1000 (adopt mode — see /ov-build:image "user_policy") |
| Home | /home/ubuntu |
Full layer stack
/ov-foundation:ubuntu— Ubuntu 24.04 + bootstrap. Inherits Debian'sapt-get update && apt-get install -y --no-install-recommends curl ca-certificates gnupgpattern becausebuild.yml distro.ubuntudeclaresinherits: debian. Ubuntu-specific:base_user: { name: ubuntu, uid: 1000, gid: 1000, home: /home/ubuntu }— nouseraddstep emitted./ov-foundation:pixi— pixi package manager + env paths (/home/ubuntu/.pixi)./ov-coder:nodejs— Node.js + npm (genericnodejs, notnodejs24)./ov-coder:build-toolchain— same Debian-devpackages as/ov-foundation:debian-builder.
Adopt-mode semantics
When the generator emits the Containerfile for this image, the bootstrap section contains:
# User ubuntu (uid=1000) adopted from base image (declared in build.yml distro.base_user) — no useradd needed
WORKDIR /home/ubuntu
USER 1000
No useradd, no groupadd, no usermod -l rename. The upstream ubuntu:ubuntu account is honored verbatim — HOME, npm prefix, pixi env, cargo home, sudoers all derive from resolved.User = "ubuntu". See /ov-build:image "user_policy" and /ov-dev:generate "writeBootstrap".
Role in the build system
Declares builds: [pixi, npm, cargo] and is referenced from ubuntu: as:
ubuntu:
builder:
pixi: ubuntu-builder
npm: ubuntu-builder
cargo: ubuntu-builder
During ov image build ubuntu-coder, cargo/npm/pixi-owning layers get their FROM ubuntu-builder AS <layer>-<type>-build stages from this image, then COPY --from=<stage> --chown=1000:1000 /home/ubuntu /home/ubuntu into the final ubuntu-coder. (The --chown=1000:1000 numeric form works uniformly regardless of user name — see /ov-coder:build-toolchain for the builder-artifact COPY pattern.)
Cross-distro sibling builders
/ov-foundation:fedora-builder— RPM-family,user:useruid 1000 (create)./ov-foundation:debian-builder— deb-family, Debian 13,user:user(create — Debian 13 ships no pre-existing uid-1000 user)./ov-foundation:archlinux-builder— pacman-family,user:user+yayfor AUR.
The three builders have near-identical layer stacks (pixi + nodejs + build-toolchain). The only meaningful divergence is this image's adopt-mode ubuntu:ubuntu identity.
Quick start
ov image build ubuntu-builder
ov shell ubuntu-builder # drops you into /home/ubuntu as uid 1000
id # uid=1000(ubuntu) gid=1000(ubuntu)
Typically not invoked directly — it's a build-time dependency of /ov-coder:ubuntu-coder.
Verification
ov image list | grep ubuntu-builderov shell ubuntu-builder -- id→uid=1000(ubuntu) gid=1000(ubuntu)ov shell ubuntu-builder -- pixi --version && node --version && gcc --version
Related images
/ov-foundation:ubuntu— parent base; declaresbase_user:inbuild.yml./ov-coder:ubuntu-coder— the consumer that this builder serves./ov-foundation:debian-builder— deb-family sibling without adopt mode./ov-foundation:fedora-builder— canonical RPM-family sibling.
Related layers
/ov-foundation:pixi,/ov-coder:nodejs,/ov-coder:build-toolchain
Related commands
/ov-build:build—base_user:declaration format inbuild.yml distro.*/ov-build:image—user_policy:field (auto / adopt / create) and the decision table/ov-build:generate— adopt-vs-create writeBootstrap emission modes
When to use this skill
MUST be invoked when:
- Building or troubleshooting
ubuntu-builderitself. - Debugging multi-stage COPY-from errors or permission issues in a
ubuntu-coderbuild (this is the source stage; uid 1000 =ubuntuby adoption). - Understanding why
${HOME}=/home/ubuntu(not/home/user) inside builder stages.
Related Skills
overthinkos/agents
development
VerifiedTrustedCommunity
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?".
SKILL.mdUpdated May 31, 2026
overthinkos/workspace-mount
tools
VerifiedTrustedCommunity
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).
SKILL.mdUpdated May 30, 2026
overthinkos/android
development
VerifiedTrustedCommunity
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`.
SKILL.mdUpdated May 26, 2026
overthinkos/git-workflow
tools
VerifiedTrustedCommunity
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.
SKILL.mdUpdated May 25, 2026