IPv6 & ssh "Too many colons"

[blaggacao]

docker-machine --native-ssh ssh dev
dial tcp: too many colons in address fe80::215:5dff:fe5f:100:22

docker-machine version
docker-machine.exe version 0.5.6, build 61388e9

I've heard the IPv6 must be handeled in [fe80::215:5dff:fe5f:100]:22 format

[blaggacao]

ref: #1616

[nathanleclaire]

Can you provide a few more details about how you've created the machine? driver, etc.

It's been pretty implicit in GetIP so far that it means IPv4, although I'm not crazy about that.

[blaggacao]

Of course:
I'm using the hyper-v driver on windows 10.

For some reasons I cannot make an external network switch working. I guess it's for incompatibilities of my SOHO router, without knowing if this is a reasonable suspect.

Therefore I work with the "internal" switch and network sharing, which is adviced at some place in the internet, but comes with it's own set of problems.

The so called "internal" switch however does not provide dhcp and the guest seems to rely on the link-local 169.254.0.0/16 address equivalent in ipv6 (fe80:).

I have managed to work around by installing a dhcp server on the host and enabling it for the virtual interface.

However, this is a multiple error situation, people might encounter when working with hyper-v, so if docker machine would work, or even give a hint about that this is a link-local 169.254.0.0/16 equivalent and what this means, this would get docker-machine out of the line.

[blaggacao]

I can't right now find the docker commit, that includes ipv6 support for the docker -H option. But it exists and will make it into 1.10...

[blaggacao]

I think this can be burried on behalf of mobylinux and docker windows support