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

Barkeep Vagrant setup breaks ~/.ssh/config #442

Closed
superduper opened this issue May 20, 2013 · 5 comments
Closed

Barkeep Vagrant setup breaks ~/.ssh/config #442

superduper opened this issue May 20, 2013 · 5 comments

Comments

@superduper
Copy link

Hi there! I've tried to install barkeep with vagrant, but it errors on ssh key copy. Cause is broken ~/.ssh/config after install. I have latest vagrant and ruby 2.0.0-p0.

Thats the content of my ~/.ssh/config after setup :)

  1 There were warnings and/or errors while loading your Vagrantfile.
  2 Your Vagrantfile was written for an earlier version of Vagrant,
  3 and while Vagrant does the best it can to remain backwards
  4 compatible, there are some cases where things have changed
  5 significantly enough to warrant a message. These messages are
  6 shown below.
  7
  8 Warnings:
  9 * `config.vm.customize` calls are VirtualBox-specific. If you're
 10 using any other provider, you'll have to use config.vm.provider in a
 11 v2 configuration block.
 12 Host barkeep_vagrant
 13   HostName 127.0.0.1
 14   User vagrant
 15   Port 2250
 16   StrictHostKeyChecking no
 17   PasswordAuthentication no
 18   IdentityFile "/Users/foobar/.vagrant.d/insecure_private_key"
 19   IdentitiesOnly yes
 20   LogLevel FATAL
@gvt
Copy link

gvt commented Jul 18, 2013

+1

I just got this on a new barkeep install with pre-existing Vagrant on the system and a pre-existing ~/.ssh/config on my Apple Macbook system.

@mhalverson
Copy link

+1

Same thing that happened to gvt also happened to me.

@dmac dmac closed this as completed in bb24f22 Sep 27, 2013
@superduper
Copy link
Author

@dmacdougall I wonder how does that fixes this ticket? :)

@dmac
Copy link
Contributor

dmac commented Sep 27, 2013

The warning you see is output by vagrant because our Vagrantfile was written for an older version. Upgrading removes that warning message.

@superduper
Copy link
Author

Cool, that makes sense. Thanks for the explanation. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants