[docs] question: confirm Forgejo runner label (CI assumes runs-on: ubuntu-latest + container jobs) #4

Closed
opened 2026-10-23 21:25:28 -05:00 by nicolas_naranjo · 1 comment
Owner

question: for @infra —

.forgejo/workflows/ci.yaml assumes the Forgejo runner registers with the label ubuntu-latest and that jobs use container: images (rust:1-slim, oven/bun:1). GitHub-style labels (ubuntu-latest, ubuntu-22.04, ...) are convention-dependent on Forgejo runner setups — some register with custom labels (e.g. docker, linux-amd64).

If the registered label differs, every job lands as waiting forever. Please confirm:

  1. the exact runs-on label(s) the runners at git.yhkze.net register, and
  2. that the runner has the docker backend (jobs use container: images; a shell-only backend would need image-less steps).

If the label needs changing, say which and the docs agent will fix .forgejo/workflows/ci.yaml in the same PR. Related: tracking issue #3.

question: for @infra — `.forgejo/workflows/ci.yaml` assumes the Forgejo runner registers with the label `ubuntu-latest` and that jobs use `container:` images (`rust:1-slim`, `oven/bun:1`). GitHub-style labels (`ubuntu-latest`, `ubuntu-22.04`, ...) are convention-dependent on Forgejo runner setups — some register with custom labels (e.g. `docker`, `linux-amd64`). If the registered label differs, every job lands as `waiting` forever. Please confirm: 1. the exact `runs-on` label(s) the runners at git.yhkze.net register, and 2. that the runner has the docker backend (jobs use `container:` images; a shell-only backend would need image-less steps). If the label needs changing, say which and the docs agent will fix `.forgejo/workflows/ci.yaml` in the same PR. Related: tracking issue #3.
Ghost added this to the SCRUM project 2026-10-23 22:39:21 -05:00
Author
Owner

Resolved by reality: the runner label works (jobs ran all night), and !25/!27 replaced the assumptions this question was about — runner job images now come from git.yhkze.net/actions/ubuntu:{act-latest,act-22.04} LAN mirrors (see gitops/charts !1, !2). Closing.

Resolved by reality: the runner label works (jobs ran all night), and !25/!27 replaced the assumptions this question was about — runner job images now come from `git.yhkze.net/actions/ubuntu:{act-latest,act-22.04}` LAN mirrors (see gitops/charts !1, !2). Closing.
Sign in to join this conversation.
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#4
No description provided.