These are chat archives for docker/machine

11th
May 2016
Elliot Wright
@SeerUK
May 11 2016 15:45
I think the main problem will be that if you are using a different driver, you will get different output with that. That key is specific to whatever driver you're using. I don't know of any other way you could get it, if that's not what docker-machine ip <name> reports.
@remram44 ssh -x -C docker@(docker-machine ip <name>). Password is tcuser.
(The above would work in Fish, substitute the syntax to work on whatever shell you're using.)
Remi Rampin
@remram44
May 11 2016 15:53
@SeerUK: ?
Elliot Wright
@SeerUK
May 11 2016 15:54
That is how you would connect. SSH into it, with the docker username, and the IP address of the machine.
The password is tcuser.
There might be a key you can get out of it so you don't have to specify a password, I didn't check :)
Remi Rampin
@remram44
May 11 2016 15:54
tcuser? What driver are you talking about?
Elliot Wright
@SeerUK
May 11 2016 15:55
That first message I put earlier was not for you, just the one with your name in :)
Remi Rampin
@remram44
May 11 2016 15:55
Yeah but it does change depending on drivers
I hardly think that docker-machine provisions AWS instances with a password as simple as tcuser
Elliot Wright
@SeerUK
May 11 2016 15:56
Aah, I see what you mean now.
tcuser will be for boot2docker drivers.
Remi Rampin
@remram44
May 11 2016 15:57
I can already connect to boot2docker specifically; what I need is a generic way to connect to any machine that docker-machine supports
Elliot Wright
@SeerUK
May 11 2016 15:57
Right, that makes sense.
Remi Rampin
@remram44
May 11 2016 15:57
:)
Elliot Wright
@SeerUK
May 11 2016 15:58
I think you may have to either use the generic driver, or use the driver-specific methods available.
I know the generic driver allows you use a key file, and specify an SSH user.
Remi Rampin
@remram44
May 11 2016 16:09
I'll just wait for #1981