ci: fix JS-action node failure (runner images) #11

Closed
nicolas_naranjo wants to merge 4 commits from fix/ci-runner into master
Owner

What

Both CI jobs failed with exec: "node": executable file not found in $PATH (exit 126): JS actions (checkout/cache) run inside the job container, and rust:1-slim ships no node while oven/bun:* ships a broken bun-node-fallback shim (verified locally with docker: node --version under oven/bun errors with Missing script to execute).

Fix

  • Both jobs → catthehacker/ubuntu:act-latest (node 24 verified in-image).
  • Toolchains move into steps: rustup minimal + rustfmt/clippy (PATH via GITHUB_PATH), bun via install script.
  • Cache kept (cargo registry/rustup/target; web node_modules + bun cache).

Gates

CI itself is the gate — this PR exercises the new config end to end. fmt/clippy/test unchanged.

## What Both CI jobs failed with `exec: "node": executable file not found in $PATH` (exit 126): JS actions (checkout/cache) run inside the job container, and `rust:1-slim` ships no node while `oven/bun:*` ships a broken bun-node-fallback shim (verified locally with docker: `node --version` under oven/bun errors with `Missing script to execute`). ## Fix - Both jobs → `catthehacker/ubuntu:act-latest` (node 24 verified in-image). - Toolchains move into steps: rustup minimal + rustfmt/clippy (PATH via GITHUB_PATH), bun via install script. - Cache kept (cargo registry/rustup/target; web node_modules + bun cache). ## Gates CI itself is the gate — this PR exercises the new config end to end. fmt/clippy/test unchanged.
ci: runner images need a working node for JS actions
Some checks failed
ci / rust (pull_request) Failing after 10m12s
ci / web (pull_request) Has been cancelled
8c0f8d2839
actions/checkout and actions/cache execute inside the job container
and require node; rust:1-slim has none and oven/bun's is a broken bun
shim (exec 'node': not found, exit 126). Both jobs now run in
catthehacker/ubuntu:act-latest (node 24 preinstalled) with toolchains
installed in steps (rustup minimal, bun install script) and cache
wired through GITHUB_PATH.
ci: fix PATH ordering — rustup not on PATH for component add
Some checks failed
ci / rust (pull_request) Failing after 16m23s
ci / web (pull_request) Has been cancelled
1a020be2ed
ci: stop depending on GITHUB_PATH — symlink toolchains into /usr/local/bin
Some checks failed
ci / web (pull_request) Has been cancelled
ci / rust (pull_request) Has been cancelled
891780cf52
Runner-version-dependent GITHUB_PATH propagation (or an unset
GITHUB_PATH redirect) would drop cargo/bun between steps and fail them
with command-not-found. The job container persists across steps, so
symlinks in /usr/local/bin cover every step; steps also re-add the
toolchain dirs to PATH defensively.
ci: drop actions/cache — runner cannot clone it reliably
Some checks failed
ci / web (pull_request) Has been cancelled
ci / rust (pull_request) Has been cancelled
fbe84037b2
The runner git-clones actions from code.forgejo.org; the cache action
clone times out intermittently (curl 28 / early EOF) before any step
runs, failing the whole job. Cache was a nice-to-have; cold builds are
slower but deterministic. Toolchain install + PATH handling unchanged.
nicolas_naranjo closed this pull request 2026-10-23 22:46:14 -05:00
Author
Owner

Superseded: the root cause moved. With egress to code.forgejo.org and static.rust-lang.org unusable from the runner host, no in-job install strategy is reliable — CI now uses a prebaked runner image (git.yhkze.net/k8s-services/rgxr-ci, from deploy/ci.Dockerfile) with toolchains and warm dependency caches, pulled over LAN. See the ci/runner-image PR.

Superseded: the root cause moved. With egress to code.forgejo.org and static.rust-lang.org unusable from the runner host, no in-job install strategy is reliable — CI now uses a prebaked runner image (git.yhkze.net/k8s-services/rgxr-ci, from deploy/ci.Dockerfile) with toolchains and warm dependency caches, pulled over LAN. See the ci/runner-image PR.
Some checks failed
ci / web (pull_request) Has been cancelled
ci / rust (pull_request) Has been cancelled

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
k8s-services/rgxr!11
No description provided.