agents/ci-base
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
In-house CI base image (python:3.12 + node 20 + docker CLI/buildx). Used by .forgejo/workflows/ci.yml in sibling agents/ repos.
5 commits 1 branch 0 tags 32 KiB
  • Dockerfile 100%
Find a file
Exact
Justin Belec 6547b93993
All checks were successful
Build ci-base image / build-push (push) Successful in 6s
Details
chore: pre-install eslint@9 to prevent CI hang 
npx eslint@9 without --yes hangs in non-interactive containers
waiting for install confirmation. Baking it in eliminates the
download entirely and speeds up CI runs.
2026-05-02 11:23:53 -05:00
.forgejo/workflows Remove debug step (docker socket fix confirmed green) 2026-04-16 23:04:04 +00:00
Dockerfile chore: pre-install eslint@9 to prevent CI hang 2026-05-02 11:23:53 -05:00
README.md Initial ci-base: python:3.12-bookworm + node 20 + docker CLI/buildx 2026-04-16 22:42:53 +00:00

README.md

ci-base

In-house CI base image used by Forgejo Actions workflows across the agents/ namespace. Avoids the supply-chain exposure of third-party Docker Hub CI images (act images, cimg, nikolaik, etc.) by building our own from the official python:3.12-bookworm (Python Software Foundation) and adding:

  • Node 20 (NodeSource official APT repo) — required for JS-based Forgejo actions: actions/checkout, actions/cache, actions/setup-python, docker/login-action, docker/build-push-action, etc.
  • Docker CLI + buildx plugin (Docker Inc official APT repo) — required for build-push jobs. The Forgejo runner mounts the host Docker socket into every job via docker_host: automount in its config.
  • Common build toolchain (build-essential, libffi-dev, image/XML development headers) — covers wheels that compile at install time: Pillow, lxml, bcrypt, faster-whisper, pymupdf.

Published tags

  • git.lab.lostsource.net/agents/ci-base:latest
  • git.lab.lostsource.net/agents/ci-base:bookworm-py312-node20
  • git.lab.lostsource.net/agents/ci-base:<short-sha> (per-commit snapshot)

Rebuild

Push any change to the Dockerfile on main and the build.yml workflow rebuilds + pushes :latest and a fresh :<short-sha> tag. Manual rebuild via Actions UI -> Run workflow.

Using it

# .forgejo/workflows/ci.yml in any agents/* repo
jobs:
  test:
    runs-on: ubuntu-latest
    container:
      image: git.lab.lostsource.net/agents/ci-base:latest
    steps:
      - uses: actions/checkout@v4
      ...