-
Notifications
You must be signed in to change notification settings - Fork 183
vagrant up asks for docker password #79
Comments
I managed to solve this by adding the username and password for the ssh user to my Vagrantfile:
|
See that merged-PR : dduportal#5 (comment) . => Add it to the vagrantfile.tpl, it's vagrant >= 1.6.x backward compatible :) |
Just put into your it should work as expected next time. (Maybe you need to destroy vm to make it working) |
Yup. Adding |
It seems like it was only a temporary fix.
|
hum.. that was wierd. I just had to wait until it timed out (without providing any password or sending any keystrokes) and then it continued the process. |
@karlingen : don't forget to remove the line |
@dduportal I don't have that line anywhere in my file. Vagrantfile:
and my Vagrantfile.host:
|
I managed to solve this by removing the two boot2docker key files located in |
I'm having this problem with Vagrant 1.7.2 and the following Vagrantfile:
I still get the password prompt for docker@127.0.0.1 whether I have insert_key=false Is there any way around this other than the two aforementioned methods? Thanks! |
Hi @davidthewatson : can you provide us the vagrant debug log ?
Thanks ! |
I am having this issue. I've tried adding config.ssh.insert_key = false to the Vagrantfile, and deleting the boot2docker ssh keys. I've pasted the debug log from vagrant up in the gist below. Vagrantfile:
https://gist.github.com/bantonj/4e6f5d4e89595bfd1683 I appreciate any help. Thanks. |
Hello @bantonj , it seems that you have a slightly different problem. In your case, you want to rsync to the @mitchellh box (hashicorp/boot2docker in Atlas as stated by vagrant documentation on this page http://docs.vagrantup.com/v2/docker/basics.html). As written here : https://github.com/mitchellh/boot2docker-vagrant-box/blob/master/vagrantfile.tpl#L4 (supposing this is the good repository mapped to the box), we see that SSH is configured in the box to use password connexion. Your gist confirmed that at this line : https://gist.github.com/bantonj/4e6f5d4e89595bfd1683#file-gistfile1-txt-L846 So there is absolutely no ssh key at all (behaviour before was to use the vagrant insecure key - https://github.com/mitchellh/vagrant/tree/master/keys ). In this case, vagrant-rsync cannot handle it and tells you that since it cannot store the password at its level. I'm not sure how to correctly handle that :
|
Hi @dduportal , I came across the same issue when I was using a fresh installed vagrant 1.7.4. Since the change of hashicorp/boot2docker every time vagrant asks for the 'docker' user's password when rsyncing. I tried to add config.ssh.username and config.ssh.password but it didn't seem to work. The related Vagrantfile is https://github.com/amplab/tachyon/blob/master/deploy/vagrant/Vagrantfile My question is: since the project is used by many other users that may not have Mac environment, is it safe to define d.vagrant_vagrantfile = '../path/file' as stated in http://docs.vagrantup.com/v2/docker/basics.html in order to replace the default host vm box 'hashicorp/boot2docker'? Will this change force every user use the defined box even if the user is in Linux and has docker installed? Thanks a lot! |
I'm also getting this problem on vagrant |
+1 v 1.7.4 Somehow, password is "tcuser" and I found that on StackOverflow. |
+1 |
+1
|
|
https://docs.vagrantup.com/v2/vagrantfile/ssh_settings.html |
It doesn't. I've tried various combinations. I'm surprised nobody's found a solution for this in a year. I guess most people have just given up using Vagrant, and are just using native boot2docker. Too much effort to figure out the issue and a workaround, I guess. Shame. |
Quick update: I managed to log in using a couple of methods after a bit of trial and error: 1: Update VagrantFile with these settings:
I suspect setting the ssh host is what made the difference as I was getting a 'connection refused' message after I typed the 'tcuser' password. Interestingly using this method, I have to type the password twice, so I guess this is being tunnelled in some way - here's the output I get after using 'vagrant ssh'
2: The other method I used which is less onerous is just to ssh directly:
and type the 'tcuser' password. I'm thinking it would make much more sense if the boot2docker image required no password at all or alternatively could be set up to use a certificate. But this will at least get me going, so good enough for me. |
Another method: Find the VM name using:
which gives the VM machine:
and then use (substituting whatever the VM name is):
This seems to cut out having to type the password twice. |
Thanks, @huggyfee! Your method worked for me as well. |
Running vagrant 1.8.1 on OSX and getting this message when doing
So my question is, why does the default boot2docker box, provide by vagrant, use password-based authentication? Thanks all! |
Having the same experience as @vmpj and I am wondering the same thing -- why is this not a straightforward problem to solve? I am a vagrant and docker newb, so maybe there's more to it than I realize. Let me know if I can provide more info or a minimal test case. |
+1 |
I'm also facing the same error. @dduportal The reported problem doesn't seem to be fixed. Can you guys reopen this issue? |
Hello @ramsrib ! Since i'm not related to hashicorp, I'm not an "issue manager" there :) Outside this, you have to know that boot2docker will be dropped at any moment by docker:
So using boot2docker is not a long term solution, especially given the overhead of moving to "ram-based" os, with immutable state, when you are using vagrant, a tool mainly dedicated to provisionning pattern :) Given the recent ubuntu and debian os upgrade, the size of the baseboxes have lowered a lot in 2 year, and moving to a debian basebox for your vagrant docker basebox may help a lot there , gaining time for you not hitting this kind of limitation :) => If you're relying on vagrant to start your container stack, I strongly recommend you to use docker-compose:
Good luck ! |
Thanks @dduportal for the explanation. I wonder when vagrant gonna switch to Docker4mac from boot2docker. Anyway, You're right, i better use docker compose instead of depending on vagrant. |
Docker for Mac is still slow for shared files, so it might be some time. |
Vagrant file:
Vagrantfile.host:
OS: Mac OS X
10.10.1
Virtualbox:
4.3.20
Tried on both Vagrant version
1.7.2
and1.6.5
.Boot2Docker-cli version:
1.4.1
The text was updated successfully, but these errors were encountered: