Do you want to verify whether the Forgejo Runner creates its networks with enable_ipv6: true? Or do you want to take it a step further and verify that IPv6 connectivity including ip6tables NAT actually works.
@earl-warren for some reason the cascading-pr CI trigger was skipped for my latest commits:
Skipping job 'cascade' due to 'vars.CASCADE != 'no''@earl-warren thanks for the hint. I've added a documentation snippet in https://codeberg.org/forgejo/docs/pulls/242
First of all, the docker daemon needs to be configured with IPv6 support, e.g.:
# cat > /etc/docker/daemon.json <<EOF
{
"ipv6": true,
"fixed-cidr-v6": "fd00:d0ca:1::/64",
…
The pipeline for this PR fails as it requires the changes from forgejo/act#24 to be merged first.
@earl-warren thanks for the pointer. I did a first hacky implementation, and it appears to be working. Unfortunately, we can't simply hard-code EnableIPv6: true in the network creation, as this…