CI Failure: Add Forgejo CI workflows and README #1

Closed
opened 2026-03-03 14:37:02 -08:00 by ci · 2 comments
Collaborator

CI Failure Analysis

Run URL: https://git.brads.house/brad/bluesky-dicebot/actions/runs/1
Commit: c073b6c061
Workflow: Add Forgejo CI workflows and README
Branch: main

Root Cause

The workflow uses python:3.12-bookworm as the container image, but actions/checkout@v4 (a GitHub Action) requires Node.js to execute. The Python container does not have node in its PATH.

Error Log

OCI runtime exec failed: exec failed: unable to start container process: exec: "node": executable file not found in $PATH: unknown
exitcode '127': command not found

What Failed

  • Task ID: 7055, Job: test
  • Main actions/checkout@v4 step failed to execute
  • Post-step cleanup also failed for the same reason

Resolution

Change the container image in .forgejo/workflows/*.yml from python:3.12-bookworm to a Node.js-compatible image:

Option 1: Use Node.js image

container: node:20

Option 2: Use an image with both Python and Node.js

container: node:20-bookworm

Then install Python inside the container if needed:

- run: apt-get update && apt-get install -y python3 python3-pip

@agent

## CI Failure Analysis **Run URL:** https://git.brads.house/brad/bluesky-dicebot/actions/runs/1 **Commit:** c073b6c0617683fa7d921165865d1ac0d6b923de **Workflow:** Add Forgejo CI workflows and README **Branch:** main ### Root Cause The workflow uses `python:3.12-bookworm` as the container image, but `actions/checkout@v4` (a GitHub Action) requires Node.js to execute. The Python container does not have `node` in its PATH. ### Error Log ``` OCI runtime exec failed: exec failed: unable to start container process: exec: "node": executable file not found in $PATH: unknown exitcode '127': command not found ``` ### What Failed - Task ID: 7055, Job: test - Main actions/checkout@v4 step failed to execute - Post-step cleanup also failed for the same reason ### Resolution Change the container image in `.forgejo/workflows/*.yml` from `python:3.12-bookworm` to a Node.js-compatible image: **Option 1:** Use Node.js image ```yaml container: node:20 ``` **Option 2:** Use an image with both Python and Node.js ```yaml container: node:20-bookworm ``` Then install Python inside the container if needed: ```yaml - run: apt-get update && apt-get install -y python3 python3-pip ``` @agent
Owner

on it

on it
brad closed this issue 2026-03-03 14:37:46 -08:00

Good analysis. The fix is straightforward — the Python container needs Node.js for the checkout action.

Recommended fix: Use a Node.js base image and install Python dependencies:

container: node:20-bookworm

steps:
  - uses: actions/checkout@v4
  - name: Install Python
    run: |
      apt-get update
      apt-get install -y python3 python3-pip python3-venv
  # ... rest of steps

This gives you both Node.js (for actions) and Python (for your code).

Want me to push the fix? I can update the workflow files and test them.

Good analysis. The fix is straightforward — the Python container needs Node.js for the checkout action. **Recommended fix:** Use a Node.js base image and install Python dependencies: ```yaml container: node:20-bookworm steps: - uses: actions/checkout@v4 - name: Install Python run: | apt-get update apt-get install -y python3 python3-pip python3-venv # ... rest of steps ``` This gives you both Node.js (for actions) and Python (for your code). Want me to push the fix? I can update the workflow files and test them.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
3 participants
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
brad/bluesky-dicebot#1
No description provided.