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 0.3.4 doesn't support the latest virtual box #14

Open
olistik opened this issue Jun 19, 2010 · 1 comment
Open

vagrant 0.3.4 doesn't support the latest virtual box #14

olistik opened this issue Jun 19, 2010 · 1 comment

Comments

@olistik
Copy link

olistik commented Jun 19, 2010

My environment:

$ ruby -v
ruby 1.9.2dev (2010-05-31 revision 28117) [x86_64-darwin10.3.0]
$ gem list | grep vagrant
vagrant (0.4.1, 0.3.4)
OS: macosx 10.6.3
virtual box: 3.2.4 r62467

I've downloaded the base box and put it into ~/data/vagrant/boxes/
wget http://files.vagrantup.com/base.box

then I've followed the initial setup as described in the readme:

$ git clone git://github.com/jeroenvandijk/rails_test_box.git
$ cd rails_test_box
$ git submodule update --init
$ bundle install

the following command issue an error:

$ bundle exec vagrant box add base ~/data/vagrant/boxes/base.box 
=====================================================================
Vagrant experienced an error!

Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
If VirtualBox is installed, it may be an incorrect version. Vagrant currently
only supports VirtualBox 3.1.x. Please install the proper version to continue.
=====================================================================

this seems due to the fact the the Gemfile requires vagrant 0.3.4 which doesn't play well with the freshest version on virtual box which is supported by vagrant 0.4.1.

we can probably fix this by simply updating the Gemfile accordingly.

from:

$ cat Gemfile 
source :rubygems

gem "vagrant", "0.3.4"

to:

$ cat Gemfile 
source :rubygems

gem "vagrant", "0.4.1"

I'll investigate if vagrant 0.4.1 will eventually breaks something in the rest of the setup.

@jeroenvandijk
Copy link
Owner

Thanks for reporting this error. I'm happy to merge in any changes that are needed. Otherwise I'll update the Gemfile asap.

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

2 participants