New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IPv6 & ssh "Too many colons" #2824

Closed
blaggacao opened this Issue Jan 13, 2016 · 5 comments

Comments

Projects
None yet
4 participants
@blaggacao
Copy link
Contributor

blaggacao commented Jan 13, 2016

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

This comment has been minimized.

Copy link
Contributor

blaggacao commented Jan 13, 2016

ref: #1616

@nathanleclaire

This comment has been minimized.

Copy link
Contributor

nathanleclaire commented Jan 13, 2016

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

This comment has been minimized.

Copy link
Contributor

blaggacao commented Jan 13, 2016

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

This comment has been minimized.

Copy link
Contributor

blaggacao commented Jan 13, 2016

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...

@dgageot dgageot added area/ssh and removed area/ssh labels Feb 12, 2016

@blaggacao

This comment has been minimized.

Copy link
Contributor

blaggacao commented Jun 4, 2016

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

@blaggacao blaggacao closed this Jun 4, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment