archie-quality (repo-scoped, online) runs the gate. quality.yml now says runs-on: archie-quality (commit f0d8c25b, not yet pushed).
nebula (instance-wide, online, id 6) has labels self-hosted:host and ubuntu-latest:docker://docker.gitea.com/runner-images:ubuntu-latest. It runs under a
dedicated gitea-runner system user with /etc/gitea-runner/config.yaml and /var/lib/gitea-runner as the working directory, installed as the gitea-runner.service systemd unit.
gitea (id 3) and helix_runner (id 4) are both offline. Only nebula offers self-hosted now, so it is the sole target for the four deploy jobs.
Remaining
Confirm gitea-runner is in the docker group. The earlier usermod added the unused runner user instead. Without it the archied-image and agent-image jobs fail on /var/run/docker.sock, and so does any ubuntu-latest:docker:// job.
Add DEPLOY_TOKEN: a PAT with write:packages and write:repository, stored as PUT /repos/sam/archie/actions/secrets/DEPLOY_TOKEN.
Re-enable the deploy workflow: PUT /repos/sam/archie/actions/workflows/deploy/enable.
ripgrep is installed on nebula, so deploy.yml's sudo apt-get install ripgrep is
now redundant and blocks an unprivileged runner. Drop it.
Registration is done; two things remain.
**Current state**
- `archie-quality` (repo-scoped, online) runs the gate. `quality.yml` now says
`runs-on: archie-quality` (commit `f0d8c25b`, not yet pushed).
- `nebula` (instance-wide, online, id 6) has labels `self-hosted:host` and
`ubuntu-latest:docker://docker.gitea.com/runner-images:ubuntu-latest`. It runs under a
dedicated `gitea-runner` system user with `/etc/gitea-runner/config.yaml` and
`/var/lib/gitea-runner` as the working directory, installed as the
`gitea-runner.service` systemd unit.
- `gitea` (id 3) and `helix_runner` (id 4) are both offline. Only `nebula` offers
`self-hosted` now, so it is the sole target for the four deploy jobs.
**Remaining**
- Confirm `gitea-runner` is in the `docker` group. The earlier `usermod` added the unused
`runner` user instead. Without it the `archied-image` and `agent-image` jobs fail on
`/var/run/docker.sock`, and so does any `ubuntu-latest:docker://` job.
- Add `DEPLOY_TOKEN`: a PAT with `write:packages` and `write:repository`, stored as
`PUT /repos/sam/archie/actions/secrets/DEPLOY_TOKEN`.
- Re-enable the deploy workflow: `PUT /repos/sam/archie/actions/workflows/deploy/enable`.
- `ripgrep` is installed on nebula, so `deploy.yml`'s `sudo apt-get install ripgrep` is
now redundant and blocks an unprivileged runner. Drop it.
sam
changed title from Register an act_runner so CI runs on Gitea to Quality jobs ask for a label no runner offers; deploy needs a Docker-capable one2026-10-29 12:30:50 +00:00
Repo side done in bec374aa: quality.yml's check job now runs on the archie-quality runner without the sudo apt-get ripgrep install or the sudo sysctl — both are host provisioning (ripgrep installed on the runner host, userns restriction in sysctl.d), same fix as the deploy gate in 3b372b4a. The namespace check stays, without sudo. Verified: YAML parses, and task check passed on this tree (exit 0) before committing.
Still open, both live-system actions outside the repo: adding the runner user to the docker group on the runner host, and storing DEPLOY_TOKEN plus re-enabling the deploy workflow via the Gitea API. Those need a PAT with write:packages and write:repository, which only you can mint — say the word and I'll do the API calls.
Repo side done in bec374aa: quality.yml's check job now runs on the archie-quality runner without the sudo apt-get ripgrep install or the sudo sysctl — both are host provisioning (ripgrep installed on the runner host, userns restriction in sysctl.d), same fix as the deploy gate in 3b372b4a. The namespace check stays, without sudo. Verified: YAML parses, and task check passed on this tree (exit 0) before committing.
Still open, both live-system actions outside the repo: adding the runner user to the docker group on the runner host, and storing DEPLOY_TOKEN plus re-enabling the deploy workflow via the Gitea API. Those need a PAT with write:packages and write:repository, which only you can mint — say the word and I'll do the API calls.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Registration is done; two things remain.
Current state
archie-quality(repo-scoped, online) runs the gate.quality.ymlnow saysruns-on: archie-quality(commitf0d8c25b, not yet pushed).nebula(instance-wide, online, id 6) has labelsself-hosted:hostandubuntu-latest:docker://docker.gitea.com/runner-images:ubuntu-latest. It runs under adedicated
gitea-runnersystem user with/etc/gitea-runner/config.yamland/var/lib/gitea-runneras the working directory, installed as thegitea-runner.servicesystemd unit.gitea(id 3) andhelix_runner(id 4) are both offline. Onlynebulaoffersself-hostednow, so it is the sole target for the four deploy jobs.Remaining
gitea-runneris in thedockergroup. The earlierusermodadded the unusedrunneruser instead. Without it thearchied-imageandagent-imagejobs fail on/var/run/docker.sock, and so does anyubuntu-latest:docker://job.DEPLOY_TOKEN: a PAT withwrite:packagesandwrite:repository, stored asPUT /repos/sam/archie/actions/secrets/DEPLOY_TOKEN.PUT /repos/sam/archie/actions/workflows/deploy/enable.ripgrepis installed on nebula, sodeploy.yml'ssudo apt-get install ripgrepisnow redundant and blocks an unprivileged runner. Drop it.
Register an act_runner so CI runs on Giteato Quality jobs ask for a label no runner offers; deploy needs a Docker-capable oneRepo side done in
bec374aa: quality.yml's check job now runs on the archie-quality runner without the sudo apt-get ripgrep install or the sudo sysctl — both are host provisioning (ripgrep installed on the runner host, userns restriction in sysctl.d), same fix as the deploy gate in3b372b4a. The namespace check stays, without sudo. Verified: YAML parses, and task check passed on this tree (exit 0) before committing.Still open, both live-system actions outside the repo: adding the runner user to the docker group on the runner host, and storing DEPLOY_TOKEN plus re-enabling the deploy workflow via the Gitea API. Those need a PAT with write:packages and write:repository, which only you can mint — say the word and I'll do the API calls.
Fixed in
bec374aaand pushed to main. Gate: task check exited 0 on the committed tree.