I’m playing through some of the tutorial materials on docs.docker.com. I want deploy docker containers on some of our internal VMs; these VMs are configured with IPv6 access only. I run into trouble very quickly.
For example, let’s go straight to the hello world test:
sds@sds:~/docker/test$ sudo docker run hello-world Unable to find image 'hello-world:latest' locally docker: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp 126.96.36.199:443: connect: network is unreachable. See 'docker run --help'.
registry-1.docker.io looks like it has a set of A records that point straight to AWS EC2 hosts. Related, index.docker .io is slightly different: it appears to point to an ELB instance but it also doesn’t have any AAAA records.
Are there any alternative names to point the docker tools at in order to boostrap a docker environment?