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

2026-06-26T12:18:37Z

k.renner commented

2026-06-26 12:18:37 +00:00

Woodpecker creates per-pipeline networks WITHOUT IPv6 unless WOODPECKER_BACKEND_DOCKER_ENABLE_IPV6=true. The daemon.json only covered the default bridge, which steps do not use — so step containers still had no v6. This sets the agent flag (pairs with daemon.json NAT) and defers the agent restart so the self-deploy survives.

k.renner added 1 commit 2026-06-26 12:18:37 +00:00

woodpecker-agent: enable IPv6 on pipeline networks (the actual fix) 1879d17dc9

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>

k.renner merged commit b50ee03d3f into master

2026-06-26 12:18:40 +00:00

k.renner referenced this issue from a commit

2026-06-26 12:18:40 +00:00

Merge pull request 'woodpecker-agent: enable IPv6 on pipeline networks (the actual fix)' (#52) from agent-woodpecker-ipv6 into master

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: konairius/homelab#52