ci: drop the BUILD_NETWORK=host workaround, the runner resolves DNS again #24
No reviewers
Labels
No labels
bug
enhancement
needs-info
needs-triage
ready-for-agent
ready-for-human
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
vicoli-oss/docker-forgejo-mcp!24
Loading…
Reference in a new issue
No description provided.
Delete branch "piscis/forgejo-image-ci"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #22. Reverts the workaround from #23: the runner's firewall was blocking outbound DNS (UDP port 53), and that's fixed now.
Summary
The Makefile is back to what #20 merged. #23's other two changes stay:
persist-credentials: falseand the digest-pinnedtonistiigi/binfmt.How it was verified
apk add git→DNS: transient error44f8614, the PR run plus two concurrent dispatchesRUNsteps didn't use--network host, so their cache didn't apply:apk addran for amd64 and arm64 (26 packages per run), noDNS:errors,PASS: 156 tools listedon both architecturesMerge Danger
Door: two-way
If the firewall blocks port 53 again, CI goes red at
apk add. Reverting this PR brings the workaround back.Blast Radius: CI
Only
ci's build step changes. Build steps no longer share the dind container's network namespace, which removes the extra path to the daemon that #23 opened.