blumeops/argocd/manifests/forgejo-runner/Dockerfile
Erich Blume 15976f90d6
All checks were successful
Test CI / test (pull_request) Successful in 0s
Reorganize CI/CD bootstrap phases, add custom runner Dockerfile
- Reorder phases: P2 is now Custom Runner Image (was Mirror & Build)
- Add P3 for Mirror Forgejo & Build from Source
- Rename P3 -> P4 (Self-Deploy), P4 -> P5 (Container Builds)
- Update overview with new phase structure and host mode notes
- Add Dockerfile for custom runner with Node.js, npm, docker, build tools
- Address chicken-and-egg problem: bootstrap manually, then automate
- Document cross-compilation challenge for macOS ARM64 target

Key insight: Stock runner lacks Node.js, so actions/checkout@v4 doesn't
work. Building custom runner image is prerequisite for everything else.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-23 18:18:23 -08:00

23 lines
566 B
Docker

FROM code.forgejo.org/forgejo/runner:3.5.1
# The base image is Debian-based
# Install tools needed for GitHub Actions and builds
RUN apt-get update && apt-get install -y --no-install-recommends \
# Required for actions/checkout and other Node-based actions
nodejs \
npm \
# Build essentials
git \
curl \
wget \
jq \
make \
gcc \
g++ \
# For container builds
ca-certificates \
docker.io \
&& rm -rf /var/lib/apt/lists/*
# Verify tools are available
RUN node --version && npm --version && docker --version