Before: with openssh-keygen in 12.11.1-ci11 (#17), zegit's SSHSIG oracle test still failed on this runner. ssh-keygen -Y verify answered "No user exists for uid 1000" (exit 255), because the pod runs as uid 1000, which has no /etc/passwd entry (zegit#575, Gitea run 25467 job 56050). v0.1.56 is still blocked.
After: the image adds a runner user and group for uid/gid 1000, with a home directory, and a build step running as uid 1000 signs and verifies an SSHSIG, so a missing entry fails the build.
How: checked on the operator workstation. zegit's test fails in ci11 run as --user 1000 and passes in this build.
Publishing takes the build workflow run with tag 12.11.1-ci12. Then flux-config re-pins the runner pods to it.
<!-- claude-projects-attribution: {"github_login":"AtomicBackspace"} -->
_Requested by **Markus** · [project thread](https://claude.ai/code/project/chan_01VZVzJf1ggm8Ck9zzkXBenz?thread=cmsg_01VZVzJf1ggm8Ck9zzkXBenzPcV9mXjpvw2o2BHSJQ3XeX)_
Before: with `openssh-keygen` in 12.11.1-ci11 (#17), zegit's SSHSIG oracle test still failed on this runner. `ssh-keygen -Y verify` answered **"No user exists for uid 1000"** (exit 255), because the pod runs as uid 1000, which has no `/etc/passwd` entry (zegit#575, Gitea run 25467 job 56050). **v0.1.56 is still blocked.**
After: the image adds a `runner` user and group for uid/gid 1000, with a home directory, and a build step running as uid 1000 signs and verifies an SSHSIG, so a missing entry fails the build.
How: checked on the operator workstation. zegit's test fails in ci11 run as `--user 1000` and passes in this build.
**Publishing** takes the build workflow run with tag `12.11.1-ci12`. Then flux-config re-pins the runner pods to it.
Refs zegit-zoo/zegit#575
🤖 Generated with [Claude Code](https://claude.com/claude-code)
With openssh-keygen in the image (#17, 12.11.1-ci11), zegit's SSHSIG
oracle test still failed on this runner: `ssh-keygen -Y verify` answered
"No user exists for uid 1000" (exit 255). The pod runs as uid 1000, which
has no /etc/passwd entry here, and ssh-keygen looks the current user up
(zegit#575, Gitea run 25467 job 56050).
The image adds a `runner` user and group for uid/gid 1000 (when the base
has none) with a home directory, and a build step running as uid 1000
signs and verifies an SSHSIG, so a missing entry fails the build.
Checked on the operator workstation: zegit's test fails in ci11 run as
--user 1000 ("No user exists for uid 1000") and passes in this build.
Refs: zegit-zoo/zegit#575
Co-Authored-By: Claude Opus 5.5 <[email protected]>
agent
marked the pull request as ready for review 2026-11-12 16:28:03 +00:00
markus
merged commit 2ea54d15ba into master2026-11-12 19:11:09 +00:00
markus
deleted branch claude/fix/575-runner-passwd2026-11-12 19:11:10 +00:00
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.
Requested by Markus · project thread
Before: with
openssh-keygenin 12.11.1-ci11 (#17), zegit's SSHSIG oracle test still failed on this runner.ssh-keygen -Y verifyanswered "No user exists for uid 1000" (exit 255), because the pod runs as uid 1000, which has no/etc/passwdentry (zegit#575, Gitea run 25467 job 56050). v0.1.56 is still blocked.After: the image adds a
runneruser and group for uid/gid 1000, with a home directory, and a build step running as uid 1000 signs and verifies an SSHSIG, so a missing entry fails the build.How: checked on the operator workstation. zegit's test fails in ci11 run as
--user 1000and passes in this build.Publishing takes the build workflow run with tag
12.11.1-ci12. Then flux-config re-pins the runner pods to it.Refs zegit-zoo/zegit#575
🤖 Generated with Claude Code