Password is asked when I run boot2docker up

[yuriteixeira]

Boot2Docker Version: 1.3.0
Mac OS X Version: Yosemite 10.10 (14A389)
Virtual Box Version: 4.3.18 r96516
Output:

$ boot2docker start
Waiting for VM and Docker daemon to start...
.........................docker@localhost's password:

NOTE: tcuser password doesn't work for the up operation

[SvenDowideit]

there's a chance that you have more than one vm, or an old vm / iso?

can you tell me more?

[rvangundy]

I'm getting the same thing. I've destroyed other VMs in VirtualBox. This occurred from a fresh install of boot2docker. I'm running:

Boot2Docker Version: v1.3.1 r57ccdb8
Mac OS X Yosemite v10.10
Virtual Box: v4.3.18 r96516

Looks like more of #405

[DominikTo]

Same issue (brew upgraded, boot2docker upgraded, deleted vm, deleted boot2docker keys in ~/.ssh, re-run boot2docker init) - always get the password prompt after boot2docker up (which does not accept tcuser). When then logging in via boot2docker ssh at least the tcuser password is accepted, but when looking at cat /.ssh/authorized_keys on the boot2docker-vm it's definitely not the key that was created on the host system (no key at all on the host actually: cat ~/.ssh/*.pub).

boot2docker init -v shows that the newly generated key got copied over to the new vm, but the key that's actually on the vm is not the one that was shown in the copy step output of boot2docker init -v. Maybe it gets garbled somehow? The key on the vm (despite always deleting id_boot2docker* on the host for every test run) is always the same (none that actually exists on the host system).

[bukzor]

I'm having this issue today. This seems to be the cause:

$ /usr/bin/ssh -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -p 2022 -i /Users/buck/.ssh/id_boot2docker docker@localhost ip addr show dev eth1
Warning: Permanently added '[localhost]:2022' (RSA) to the list of known hosts.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0644 for '/Users/buck/.ssh/id_boot2docker' are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.
bad permissions: ignore key: /Users/buck/.ssh/id_boot2docker
docker@localhost's password:

[bukzor]

Putting correct permissions on the file seems to fix it:

$ chmod go-r ~/.ssh/id_boot2docker
$ /usr/bin/ssh -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -p 2022 -i /Users/buck/.ssh/id_boot2docker docker@localhost ip addr show dev eth1
Warning: Permanently added '[localhost]:2022' (RSA) to the list of known hosts.
4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 08:00:27:06:ec:56 brd ff:ff:ff:ff:ff:ff
    inet 192.168.59.103/24 brd 192.168.59.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fe06:ec56/64 scope link
       valid_lft forever preferred_lft forever

[SvenDowideit]

ah, so we should be able to fix that in the cli :) sweet.

[karlingen]

+1

[jackmcpickle]

Thanks @bukzor worked for me.

[ismael-rivera]

I too am also having the same issue getting

.docker@localhost's password:

[ismael-rivera]

For anybody reading this just as a heads up. You may have to type in "tcuser" around four times as the system did to me. It kept prompting me and I thought at first, it was because the password was incorrect. No, no, no... it will ask you for the password on every boot process until the VM finishes booting up. Frankly, it was only because I was frustrated and kept typing the password that I noticed the prompts had a different character at the beginning, which is why I felt the need to let everyone here know, so keep a look out for that if you are like me and where experiencing that "issue".

Which begs a few questions: why is the system asking for the password multiple times on the same state change? Is there any way to change this mode of operation in the configurations and/or the password options? Where are the configuration files?(Still new to docker, so I'll assume that I can find this info in the documents) and, finally, what security issues might arise from not changing the password in a production deployment and is it relevant for mode of?

Also, many thanks to the boot2docker team for making such a great app for us non-linux civilians. :)

[richtr]

You may have to type in "tcuser" around four times as the system did to me. It kept prompting me and I thought at first.

Thank you @theMicMac! I was having the same strange issue and entering the password four times did it.

Which begs a few questions: why is the system asking for the password multiple times on the same state change? Is there any way to change this mode of operation in the configurations and/or the password options?

Agree that it is very counter-intuitive to enter your password 4 times right now.

[karlingen]

You do not have to type it 4 times. Just keep on pressing enter without typing a password and you will get by.

$ boot2docker start
..
docker@localhost's password:
docker@localhost's password:
docker@localhost's password:
docker@localhost's password:
..

[yms9654]

+1

[yms9654]

This is solution in my case.

1. copy ~/.ssh/id_boot2docker.pub to clipboard.
2. boot2docker ssh
   (password is 'tcuser')
3. paste to ~/.ssh/authorized_keys file.
4. exit and try agin 'boot2docker start'

[swatcat92]

$ docker run ubuntu /bin/echo 'Hello world'
Post http://127.0.0.1:2375/v1.20/containers/create: dial tcp 127.0.0.1:2375: ConnectEx tcp: No connection could be made because the target machine actively refused it..

• Are you trying to connect to a TLS-enabled daemon without TLS?
• Is your docker daemon up and running?
  "how to resolve this problem can any one help me? please"

[geev03]

The ssh password for user tc is not known, so changed it and got ssh working

cut -d: -f1 /etc/passwd

passwd tc

login as: tc
tc@192.168.8.157's password:
## .
## ## ## ==
## ## ## ## ## ===
/"""""""""""""""""/ ===
~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ / ===- ~~~
____ o */
\ \ /
*______/

---

| |__ ___ ___ | ||__ \ | | ___ ___| | ___ _ __
| '_ \ / _ \ / _ | | __) / _` |/ _ \ / __| |/ / _ \ '|
| |) | () | () | | / / (| | () | (| < / |
|_./ / _/ __|,|/ _||_|_|

WARNING: this is a build from test.docker.com, not a stable release.

Could not chdir to home directory /home/tc: No such file or directory
Boot2Docker version 1.12.1-rc1, build HEAD : 0e17a04 - Mon Aug 15 18:14:57 UTC 2016
Docker version 1.12.1-rc1, build 7889dc7

[ghost]

thanks for @yms9654 , the problem has solved