agent
afed70586a
Alpine splits git-http-backend OUT of the `git` package: git alone ships git-remote-http/https but not the CGI backend. The runner therefore had git 2.52.0 and no git-http-backend, so zegit's internal/forgeprobe smart-HTTP tests failed at request time with "fork/exec git-http-backend: no such file or directory" and reported three FAILURES for a missing tool. That turned Gitea CI red on every zegit master commit while GitHub stayed green, for hours, with nobody looking — GitHub is the release oracle, which is exactly why a red mirror is invisible. Verified against the real base image, not just alpine:3 — on code.forgejo.org/forgejo/runner:12.11.1 (Alpine 3.23), `apk add git git-daemon` puts git-http-backend at /usr/libexec/git-core/git-http-backend, and `git --exec-path` resolves to that directory, which is the lookup the test harness performs.
52 lines
2.3 KiB
Docker
52 lines
2.3 KiB
Docker
# Custom toolchain image for the self-hosted Gitea Actions (Forgejo) runner.
|
|
#
|
|
# The cluster runs act_runner in *host mode* (docker disabled), so workflow steps
|
|
# execute INSIDE this image. The stock forgejo/runner image is minimal and lacks
|
|
# node (needed by JS actions: actions/checkout, setup-go, ...), git, make, etc.
|
|
# The runner pod is non-root with all caps dropped, so it cannot apt/apk-add at
|
|
# runtime -- the tools must be baked in here.
|
|
#
|
|
# Build multi-arch (cluster is mixed amd64/arm64) and push to the Gitea registry:
|
|
#
|
|
# docker buildx create --use --name zegit-ci 2>/dev/null || true
|
|
# docker login gitea.langenoja.se # username + a Gitea personal access token
|
|
# docker buildx build --platform linux/amd64,linux/arm64 \
|
|
# -t gitea.langenoja.se/zegit-zoo/zegit-forgejo-runner:12.11.1-ci --push .
|
|
#
|
|
# Then in flux-config set both containers' image: to the tag above and commit.
|
|
# Package visibility is PUBLIC, so the runner namespace pulls without a secret.
|
|
FROM code.forgejo.org/forgejo/runner:12.11.1
|
|
|
|
USER root
|
|
|
|
# nodejs -> JS actions runtime (actions/checkout, actions/setup-go, ...)
|
|
# git -> checkout
|
|
# git-daemon -> provides git-http-backend, which Alpine splits OUT of the `git`
|
|
# package (git alone ships git-remote-http/https but NOT the CGI
|
|
# backend). Without it, internal/forgeprobe's smart-HTTP tests died
|
|
# with "fork/exec git-http-backend: no such file or directory" and
|
|
# reported three FAILURES for a missing tool — which turned Gitea CI
|
|
# red on every zegit master commit while GitHub stayed green, for
|
|
# hours, unnoticed.
|
|
# bash -> `shell: bash` steps and many action entrypoints
|
|
# coreutils-> GNU userland (alpine busybox tools trip up some scripts)
|
|
# curl,tar -> setup-go / gitleaks download + extract their own arch-specific binaries
|
|
# make -> zegit Makefile targets
|
|
# ca-certificates -> trusted roots for HTTPS to gitea/github/goproxy
|
|
#
|
|
# Go is intentionally NOT baked in: actions/setup-go fetches the pinned version
|
|
# per-run (node + tar are present), so the image needs no rebuild on Go bumps.
|
|
RUN apk add --no-cache \
|
|
nodejs \
|
|
git \
|
|
git-daemon \
|
|
bash \
|
|
coreutils \
|
|
curl \
|
|
tar \
|
|
make \
|
|
ca-certificates
|
|
|
|
# Match the runner pod's runAsUser (1000); keep the image non-root by default.
|
|
USER 1000
|