fix: runner DNS resolution and stale registration #7

mvhutz · 2026-03-16T02:00:42Z

mvhutz commented

2026-03-16 02:00:42 +00:00

Summary

Fix etc_hosts templating — dict key was rendered as literal {{ server_fqdn.value }} instead of the actual domain
Clear runner data volume on each deploy to prevent stale registration errors when the token changes
Use instance-level registration token for global runner access

Test plan

/etc/hosts in runner container shows git.maximhutz.com mapped to 10.0.1.2
Runner registers and connects successfully
Verify runner picks up jobs from any repo

🤖 Generated with Claude Code

## Summary - Fix `etc_hosts` templating — dict key was rendered as literal `{{ server_fqdn.value }}` instead of the actual domain - Clear runner data volume on each deploy to prevent stale registration errors when the token changes - Use instance-level registration token for global runner access ## Test plan - [x] `/etc/hosts` in runner container shows `git.maximhutz.com` mapped to `10.0.1.2` - [x] Runner registers and connects successfully - [ ] Verify runner picks up jobs from any repo 🤖 Generated with [Claude Code](https://claude.com/claude-code)

mvhutz added 1 commit 2026-03-16 02:00:42 +00:00

fix: runner DNS resolution and stale registration data 539f8cda2f

Fix etc_hosts templating so the runner resolves the gitea domain to
the private IP. Clear runner data volume on deploy to avoid stale
registration errors when the token changes.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

mvhutz merged commit 3f724dbdfd into main

2026-03-16 02:00:54 +00:00

mvhutz deleted branch fix/runner-dns-registration

2026-03-16 02:00:54 +00:00

mvhutz referenced this issue from a commit

2026-03-16 02:00:56 +00:00

fix: runner DNS resolution and stale registration (#7)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: web/git#7