woodpecker-agent: enable IPv6 on pipeline networks (the actual fix) #52

Merged
k.renner merged 1 commits from agent-woodpecker-ipv6 into master 2026-06-26 12:18:40 +00:00
1 Commits
Author SHA1 Message Date
k.rennerandClaude Opus 4.8 1879d17dc9 woodpecker-agent: enable IPv6 on pipeline networks (the actual fix)
The daemon.json (PR #48) only gives the *default bridge* IPv6 — but
Woodpecker runs each step on a per-pipeline network, which it creates
WITHOUT IPv6 unless told to. So step containers still had no v6 and the
deploy to v6-only proxy-1 kept failing 'Network unreachable'.

Set WOODPECKER_BACKEND_DOCKER_ENABLE_IPV6=true on the agent so it creates
v6-enabled pipeline networks (pairs with the daemon.json ipv6/ip6tables
NAT). Also defer the woodpecker-agent restart (systemd-run timer) so the
agent self-deploy doesn't interrupt its own running pipeline.

Ref: https://woodpecker-ci.org/docs/administration/configuration/backends/docker

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-26 14:18:36 +02:00