Container loopback IPv6 support
D
David Keller
As IPv6 compatibility becomes a requirement, our applications handle it, hence associated unit tests as well.
But on containers, IPv6 is disabled i.e. opening an IPv6 socket on loopback interface fails, so IPv6 related tests can't run.
There is a FAQ entry about this, but it requires VM build, which is slower.
CCI-I-571
p
pavel.odintsov@gmail.com
It will be extremely helpful to have IPv6 connectivity for VMs as so many open source projects like our https://github.com/pavel-odintsov/fastnetmon/ rely on CircleCI for builds and testing.
We have IPv6 support in our product but to polish it and test it on routine basis CI need to have support for IPv6 too.
Even some basic things can be easily caught just by enabling IPv6 in Docker or VMs.
Another thing which may clearly benefit from IPv6 is SSH access.
So instead of using random ports you can just use unique IPv6 addresses and use standard port which is 22 for that.
G
Grant Erickson
This is critical for Project Connected Home over IP.