The proxy on v6-only proxy-1 could not reach the management server (no Docker IPv6, no v4). Adds daemon.json ipv6+ip6tables, restarts docker before deploy, and puts the proxy on the v6-capable default bridge.
The proxy on v6-only proxy-1 could not reach the management server (no Docker IPv6, no v4). Adds daemon.json ipv6+ip6tables, restarts docker before deploy, and puts the proxy on the v6-capable default bridge.
The deployed proxy on proxy-1 (v6-only host) couldn't connect to the
management server: 'dial tcp [2a01:...]:443 / 162.55.50.97:443: network is
unreachable'. The host reaches mgmt over v6 fine, but Docker had no IPv6
(no daemon.json), so the container had no v6 egress and no v4 exists.
Add /etc/docker/daemon.json (ipv6 + ULA fixed-cidr-v6 + ip6tables NAT),
flush it (restart docker) before the container deploys, and put the proxy
service on the default bridge (network_mode: bridge) so it inherits that v6.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
The proxy on v6-only proxy-1 could not reach the management server (no Docker IPv6, no v4). Adds daemon.json ipv6+ip6tables, restarts docker before deploy, and puts the proxy on the v6-capable default bridge.