Is there a known issue with IPv6 addresses and the latest runners?
I’ve always used IPv6 ever since you introduced it based on this thread: Listing of runner's IPv6 addresses? - #2 by codefloe
In particular, I whitelisted crow runners in my private network’s FW. Lately I am getting errors that crow can’t reach my server:
TASK [Gathering Facts] *********************************************************
[ERROR]: Task failed: Failed to connect to the host via ssh: ssh: connect to host 2a01:4f8:1c19:d14d::1 port 22: Network unreachable
**fatal: [toolserver]: UNREACHABLE! => {“changed”: false, “msg”: “Task failed: Failed to connect to the host via ssh: ssh: connect to host xxxx:yyyy:1c19:d14d::1 port 22: Network unreachable”, “unreachable”: true}
**
It’s clearly a FW block on my side that happened because the IPv6 I had previously didn’t work.
(In the meantime I’ve whitelisted the IPv4 and everything works again.)
Preparing step
Creating container
Connecting container networks
Starting container
apk add --no-cache curl > /dev/null0s
echo "Agent IPv4:"0s
Agent IPv4:
curl -s -4 ifconfig.me0s
xx.yyy.zzz.203+ echo “Agent IPv6:”
Agent IPv6:
curl -s -6 ifconfig.me1s