I got a lot of great feedback on my last post about the basic configuration of Docker Engine with IPv6. The next topic that I wanted to cover (and was excited to test) was Docker Hub with IPv6.
My hopes and dreams were smashed in about 15 seconds when I found out that IPv6 is not enabled for hub.docker.com and none of my docker login, docker search, docker pull, docker push or even a browser session to https://hub.docker.com would work over IPv6.
An nslookup reveals no IPv6. Nada. Zip. :
> hub.docker.com Server: 184.108.40.206 Address: 220.127.116.11#53 Non-authoritative answer: hub.docker.com canonical name = elb-default.us-east-1.aws.dckr.io. Authoritative answers can be found from: > docker.com Server: 18.104.22.168 Address: 22.214.171.124#53 Non-authoritative answer: docker.com nameserver = ns-1289.awsdns-33.org. docker.com nameserver = ns-1981.awsdns-55.co.uk. docker.com nameserver = ns-207.awsdns-25.com. docker.com nameserver = ns-568.awsdns-07.net. docker.com origin = ns-207.awsdns-25.com mail addr = awsdns-hostmaster.amazon.com serial = 1 refresh = 7200 retry = 900 expire = 1209600 minimum = 86400
Insert your favorite sad panda image here. 🙁
I know the Docker folks are in a bind with this since they are using Amazon who is likely the last cloud provider on earth who does not have real IPv6 support (none in EC2-VPC but you can in EC2-Classic).
I will move on from Docker Hub and start checking out other Docker stuff like Registry, Compose, etc…
See you next time. Sorry for the epic failure of this post.