Skip to content
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

vagrant can' t connect to getting started virtual machine. #4

Closed
hef opened this issue Mar 9, 2010 · 5 comments
Closed

vagrant can' t connect to getting started virtual machine. #4

hef opened this issue Mar 9, 2010 · 5 comments
Labels

Comments

@hef
Copy link

hef commented Mar 9, 2010

I am attempting to run through the getting started tutorial.

I am on os x, and there is some kind of ssh conflict with my private ssh key on this machine.
Note that the machine has my ssh key in os x's keychain.

The machine asks for my private ssh key over and over again, but doesn't seem to accept it either way, not that it would as the VM shouldn't have my public key anyway.

Program output:
http://gist.github.com/326739

@mitchellh
Copy link
Contributor

hef,

This could be due to the script which Vagrant uses to SSH. Can you try SSHing manually:

ssh -p 2222 vagrant@localhost

The password is vagrant also. Does this work?

Feel free to jump in #vagrant if you get a chance and we can probably work this out pretty quick.

Mitchell

@hef
Copy link
Author

hef commented Mar 9, 2010

That ssh command and password got me in.

/vagrant appears to be empty in the VM

@mitchellh
Copy link
Contributor

hef,

Yeah it would be, since vagrant up never had a chance to mount the folders. It looks like the problem may be with the "spawn" script we use to launch vagrant. I'm going to do a bit more research.

Mitchell

@mitchellh
Copy link
Contributor

hef,

An update: We recently pushed an update to Vagrant which allows us to support key-based SSH connections versus passworded. Perhaps this will [somehow] fix the problem you were having, since I've had no luck in figuring out the error you have been getting and so far no one has come forward with the same issue.

The key-based SSH won't be in the gem until 0.2, but you're welcome to give it a shot straight from master (the base box online is already updated with the correct public key).

Mitchell

@mitchellh
Copy link
Contributor

I haven't heard any word on this issue in some time, so I'm going to close it. If this issue crops up again, please start a new GH issue.

Thanks,
Mitchell

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants