ci: fix workflow on minimal runner (node:20-bookworm lacks pip) #3

Merged

Mark merged 1 commit from ci-autoheal/run-5844 into main

2026-09-12 03:21:59 +00:00

Mark commented

2026-09-12 03:12:00 +00:00

Owner

Problem

Mark/crewai_vault_ops_tool Actions run #2 failed (131s). The earlier run #1 wedged at 9s (runner wedge).

Root cause: the user-level runner resolves ubuntu-latest to docker://node:20-bookworm, which has Python 3.11 but no pip and no ensurepip. The workflow called bare pip install ruff with no fallback, so the missing-pip exit 127 failed the build.

Fix

Override the task container to catthehacker/ubuntu:act-22.04 (full Ubuntu with python + pip + jq + git preinstalled). Same pattern already used in crew_transcript and clawdeploy.
Switch all pip install calls to python3 -m pip install so they don't depend on a standalone pip binary.
Keep || true on ruff lint — the project has ~20 accumulated lint errors (unused imports, E701 multi-statement); surfacing them is fine but they shouldn't gate CI. Follow up via a separate lint-cleanup card.

Verification

After merge, the CI workflow on main should run on catthehacker/ubuntu:act-22.04, install ruff successfully, and complete green regardless of pip-install project deps (which are best-effort).

## Problem `Mark/crewai_vault_ops_tool` Actions run #2 failed (131s). The earlier run #1 wedged at 9s (runner wedge). Root cause: the user-level runner resolves `ubuntu-latest` to `docker://node:20-bookworm`, which has Python 3.11 but no pip and no ensurepip. The workflow called bare `pip install ruff` with no fallback, so the missing-pip exit 127 failed the build. ## Fix - Override the task container to `catthehacker/ubuntu:act-22.04` (full Ubuntu with python + pip + jq + git preinstalled). Same pattern already used in `crew_transcript` and `clawdeploy`. - Switch all `pip install` calls to `python3 -m pip install` so they don't depend on a standalone `pip` binary. - Keep `|| true` on ruff lint — the project has ~20 accumulated lint errors (unused imports, E701 multi-statement); surfacing them is fine but they shouldn't gate CI. Follow up via a separate lint-cleanup card. ## Verification After merge, the `CI` workflow on main should run on `catthehacker/ubuntu:act-22.04`, install ruff successfully, and complete green regardless of pip-install project deps (which are best-effort).

Mark added 1 commit

2026-09-12 03:12:01 +00:00

ci: override container to catthehacker/ubuntu:act-22.04 and use python3 -m pip

CI / ci (pull_request) Successful in 2m22s

Details

6293acd51a

The previous workflow ran on the user-level runner's default container
(node:20-bookworm), which has Python 3.11 but no pip and no ensurepip.
- 'pip install -r requirements.txt' had a '|| true' fallback chain, but
  'pip install ruff' did not, so when pip was missing that step exited
  127 and failed the build.
- 'actions/setup-python@v5' on a system that already had python3.11 just
  used the system python (no pip), so pip never got installed.

Override the task container to catthehacker/ubuntu:act-22.04 so python,
pip, jq, and standard build deps are available. Switch all 'pip install'
calls to 'python3 -m pip install' so they don't depend on a standalone
pip binary in PATH.

Run URLs:
- failed: https://forgejo.tail018ac4.ts.net/Mark/crewai_vault_ops_tool/actions/runs/2 (run 5844)
- previous: https://forgejo.tail018ac4.ts.net/Mark/crewai_vault_ops_tool/actions/runs/1 (run 3670)