ci: prebaked runner image — toolchains and warm caches, LAN-pulled #18
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/runner-image"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
The runner host cannot download at job time: action clones from code.forgejo.org time out (curl 28, <100KB/s) and rustup hangs on static.rust-lang.org. No in-job install strategy survives that (PR #11 closed superseded).
What
deploy/ci.Dockerfile— prebaked runner image: catthehacker/ubuntu:act-latest + rust stable (rustfmt/clippy) + bun, cargo registry warmed for the currentCargo.lock(manifest-stub fetch), webnode_modulesbaked at/opt/web-depswith abun.locksha stamp..forgejo/workflows/ci.yaml— jobs run ingit.yhkze.net/k8s-services/rgxr-ci:latest(LAN pull); rust job = checkout + fmt/clippy/test; web job = checkout + lockfile-stamp check + restore node_modules + build. No JS actions beyond checkout, no cache action, no GITHUB_PATH dependence (symlinks + ENV PATH)..dockerignore— blanketwebexclusion scoped to build artifacts so the image can warm web deps (api/render Dockerfiles COPY only crates/manifests — unaffected).Rebuild path (documented in the Dockerfile header): from any machine with normal egress,
docker build -f deploy/ci.Dockerfile -t git.yhkze.net/k8s-services/rgxr-ci:{latest,date} . && docker push ...— required when Cargo.lock or web/bun.lock change meaningfully (the web job fails loudly on stamp mismatch).Gates
rgxr-ciis pushed to the Forgejo registry — blocked on a package-write token (needs owner). Merge after the image lands and this PR goes green.Escalation (needs human/infra decision). The
rgxr-cipush to the Forgejo registry failed consistently: 8 attempts,504 Gateway Timeoutfrom the gateway on the ~2 GB layer upload (same egress that kills job-time downloads, now on the ingest side). The image itself is built and verified locally.Options:
deploy/ci.Dockerfilein ~5 min on a normal connection, or I can push it if given GHCR creds.docker save | ssh docker load— I can produce the tar on request; zero registry involved.Since CI is in your lane now, calling it: the PR (workflow) is ready and merges once the image exists somewhere the runner can pull. If you go GHCR, only the
container.imageline changes.6488e1986806745dcdbcstatus: Claude has taken this PR over (CI is in the Rust-backend lane, #20).
Cargo.lockfix in !2406745dc: rustup-init now comes fromstatic.rust-lang.organd bun from npm (thesh.rustup.rs/bun.shinstaller domains were unreachable), andENV PATHextends the base PATH so node from/opt/acttoolcachestays visible to npm and toactions/checkout--network none, so the cargo cache really is warmblocker: pushing
git.yhkze.net/k8s-services/rgxr-cireturns 401 forrgxr-agent. It has push on the repo but is not a member of orgk8s-services, and org packages need org write. Either fix needs a human:rgxr-agentto ak8s-servicesteam with Packages: write, ordocker build -f deploy/ci.Dockerfile -t git.yhkze.net/k8s-services/rgxr-ci:latest . && docker push git.yhkze.net/k8s-services/rgxr-ci:latestNote: a ~1 GB layer through Cloudflare may also hit its upload body limit. If option 1 still fails on large blobs, push over the LAN (option 2).
status: closed in favor of !25 — CI runs on LAN mirrors of stock public images instead of a custom
rgxr-ciimage (decision in #26; the human preferred public images).deploy/ci.Dockerfileis not needed.Pull request closed