Looks like CI started failing for some reason: https://github.com/bitcoin/bitcoin/actions/runs/32003166302/job/95307313400#step:11:233:
Error response from daemon: Cannot read IPv6 setup for bridge br-5b85391ca17e: open /proc/sys/net/ipv6/conf/br-5b85391ca17e/disable_ipv6: no such file or directory
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/35991.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline and AI policy for information on the review process. A summary of reviews will appear here.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
FWIW I have pinged Warp and asked them if something has changed on the runners
dmesg says (from the ci log):
[ 1.171084] IPv6: Loaded, but administratively disabled, reboot required to enable
[ 3.049306] systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6.
Yup: I pinged them with
have the runners changed recently? We are seeing failures across the board like this: https://github.com/bitcoin/bitcoin/actions/runs/32006372751/job/95316581495?pr=35991
where we cannot set up our ipv6 docker network. Looks to me like the runner lacks the per-bridge IPv6 sysctl from
open /proc/sys/net/ipv6/conf/br-.../disable_ipv6:
no such file or directory
They say they'll have a fix out shortly for it. Will update in here when it's done.
Cool, thx
OK this is apparently fixed now