Go to file

images / hermes (push) Successful in 1m55s

Details

hermes: two-stage build, make /opt/hermes writable by uid 10000

Upstream ships /opt/hermes (app + .venv + scripts) read-only root, which
blocks the agent self-modifying and the gateway auto-installing the
WhatsApp bridge's node_modules in place. Add a derived Containerfile layer
(FROM the upstream build) that chowns/chmods /opt/hermes writable by the
runtime hermes user. Done in the image, not a volume: a volume over
/opt/hermes copies-up once then freezes the app, silently defeating
AutoUpdate=registry. Persistence stays on the /opt/data volume.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011D3YeWKpjg5bT488fVanCH

2026-06-23 18:31:32 +03:00

.gitea/workflows

hermes: two-stage build, make /opt/hermes writable by uid 10000

2026-06-23 18:31:32 +03:00

images/hermes

hermes: two-stage build, make /opt/hermes writable by uid 10000

2026-06-23 18:31:32 +03:00

.gitignore

Add lair/containers image-build repo; hermes as first image

2026-06-23 12:17:10 +03:00

readme.md

Add lair/containers image-build repo; hermes as first image

2026-06-23 12:17:10 +03:00

readme.md

lair/containers

Container images required by lair infrastructure, built and published to the Gitea registry at git.lair.cafe. Convention follows gongfoo's images/ setup.

Layout

images/<name>/          one directory per image
  Containerfile         (when we author the image ourselves)
  build.sh              local build helper
  readme.md             what it is and how it's built
.gitea/workflows/
  images.yml            builds + publishes every image, on push / daily / dispatch

Images

Image	Published as	Source
hermes	`git.lair.cafe/lair/hermes:{version,latest}`	built from NousResearch/hermes-agent's Dockerfile at the latest release tag

How builds work

Trigger: push under images/**, a daily cron poll, or manual dispatch.
Release-tracking: each image job resolves the upstream's latest release via its API and builds that exact ref. For upstreams that ship their own Dockerfile (hermes) we build directly from the upstream git context; for images we author, the version is passed as a --build-arg with the Containerfile pin as fallback.
Self-healing: a build runs only when the resolved version isn't already in the registry — and because the registry (not a committed pin) is the source of truth, a failed build simply retries on the next poll instead of stranding a stale image. (Lesson borrowed from gongfoo.)

Adding an image

mkdir images/<name>, add a Containerfile (or build from an upstream context) + build.sh + readme.md.
Add a job to .gitea/workflows/images.yml that logs in, builds git.lair.cafe/lair/<name>:latest, and pushes.
Consumers pull git.lair.cafe/lair/<name>:latest with AutoUpdate=registry.

Required secret

Secret	Purpose
`REGISTRY_TOKEN`	Gitea token with `write:package` for `git.lair.cafe`; used as `podman login -u $GITEA_ACTOR -p $REGISTRY_TOKEN`. Set in this repo's (or the `lair` org's) Actions secrets.

Build jobs run on self-hosted runners labelled metal + podman.