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 1.1 Support #416

Closed
skorfmann opened this Issue Mar 16, 2013 · 16 comments

Comments

Projects
None yet
8 participants
@skorfmann

skorfmann commented Mar 16, 2013

I'm trying to setup this with the recently release Vagrant 1.1. It doesn't seem to work properly.

Is there a known way to make it work?

@skorfmann

This comment has been minimized.

Show comment
Hide comment
@skorfmann

skorfmann Mar 16, 2013

Well, I'm just vendoring to ./cookbooks for now.

skorfmann commented Mar 16, 2013

Well, I'm just vendoring to ./cookbooks for now.

@reset

This comment has been minimized.

Show comment
Hide comment
@reset

reset Mar 16, 2013

Member

@skorfmann I'm working on Vagrant 1.1 support right now and should be done before Monday

Member

reset commented Mar 16, 2013

@skorfmann I'm working on Vagrant 1.1 support right now and should be done before Monday

@skorfmann

This comment has been minimized.

Show comment
Hide comment
@skorfmann

skorfmann Mar 16, 2013

Awesome! :) Thanks for the feedback.

skorfmann commented Mar 16, 2013

Awesome! :) Thanks for the feedback.

@milosgajdos83

This comment has been minimized.

Show comment
Hide comment
@milosgajdos83

milosgajdos83 Mar 19, 2013

I'm also interested in this :) Given that Vagrant 1.1 no longer comes packaged as ruby gem (no more bundle exec vagrant up ?), this will mean a change of workflow in Berkshelf ? ie. no more vagrant gem in Gemfile ?

milosgajdos83 commented Mar 19, 2013

I'm also interested in this :) Given that Vagrant 1.1 no longer comes packaged as ruby gem (no more bundle exec vagrant up ?), this will mean a change of workflow in Berkshelf ? ie. no more vagrant gem in Gemfile ?

@hron84

This comment has been minimized.

Show comment
Hide comment
@hron84

hron84 Mar 19, 2013

+1 user interested in 1.1 support

hron84 commented Mar 19, 2013

+1 user interested in 1.1 support

@hmalphettes

This comment has been minimized.

Show comment
Hide comment
@hmalphettes

hmalphettes Mar 20, 2013

+1 for 1.1 support and thanks for working on it so quickly.
In order to try berkshelf-1.3.0.rc1 with vagrant-1.1 support,
I ended up patching vagrant to support installing pre-released gems as vagrant plugins.

In case this is useful to someone else:
hashicorp/vagrant#1461

hmalphettes commented Mar 20, 2013

+1 for 1.1 support and thanks for working on it so quickly.
In order to try berkshelf-1.3.0.rc1 with vagrant-1.1 support,
I ended up patching vagrant to support installing pre-released gems as vagrant plugins.

In case this is useful to someone else:
hashicorp/vagrant#1461

@skorfmann

This comment has been minimized.

Show comment
Hide comment
@skorfmann

skorfmann Mar 20, 2013

@hmalphettes thanks, will give it a try tonight

skorfmann commented Mar 20, 2013

@hmalphettes thanks, will give it a try tonight

@reset

This comment has been minimized.

Show comment
Hide comment
@reset

reset Mar 20, 2013

Member

@hmalphettes thanks for opening that PR with Vagrant; now I don't have to :)

Member

reset commented Mar 20, 2013

@hmalphettes thanks for opening that PR with Vagrant; now I don't have to :)

@milosgajdos83

This comment has been minimized.

Show comment
Hide comment
@milosgajdos83

milosgajdos83 Mar 20, 2013

any estimates when will this be in stable version as oppose to rc ?

milosgajdos83 commented Mar 20, 2013

any estimates when will this be in stable version as oppose to rc ?

@reset

This comment has been minimized.

Show comment
Hide comment
@reset

reset Mar 20, 2013

Member

released as Berkshelf 1.3.1 and Berkshelf-Vagrant 1.0.2

Member

reset commented Mar 20, 2013

released as Berkshelf 1.3.1 and Berkshelf-Vagrant 1.0.2

@mitchellh

This comment has been minimized.

Show comment
Hide comment
@mitchellh

mitchellh Mar 21, 2013

I merged the patches to Vagrant that let you install a specific version and prerelease and all that. It will be part of 1.1.3 released tomorrow or Monday.

mitchellh commented Mar 21, 2013

I merged the patches to Vagrant that let you install a specific version and prerelease and all that. It will be part of 1.1.3 released tomorrow or Monday.

@reset

This comment has been minimized.

Show comment
Hide comment
@reset

reset Mar 21, 2013

Member

thanks @mitchellh!

Member

reset commented Mar 21, 2013

thanks @mitchellh!

@milosgajdos83

This comment has been minimized.

Show comment
Hide comment
@milosgajdos83

milosgajdos83 Mar 31, 2013

actually this seems to have broken Vagrant ? I have installed berkshelf-vagrant (1.0.6) and am running Vagrant 1.1.4. Yet just trying to "up" a simple box with the most simplest Vagrantfile throws an error, that Berksfile can not be found in project directory even though it's not required by Vagrantfile. Am I missing something ?

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
Berkshelf::BerksfileNotFound: No Berksfile or Berksfile.lock found at: /Users/milosgajdos/berkshelf-playground/getting-started/Berksfile

Vagrantfile:

$script = <<SCRIPT
apt-get update
apt-get upgrade
SCRIPT

Vagrant.configure("2") do |config|
  config.vm.box = "testbox"
  config.vm.provision :shell, :inline => $script 
end

milosgajdos83 commented Mar 31, 2013

actually this seems to have broken Vagrant ? I have installed berkshelf-vagrant (1.0.6) and am running Vagrant 1.1.4. Yet just trying to "up" a simple box with the most simplest Vagrantfile throws an error, that Berksfile can not be found in project directory even though it's not required by Vagrantfile. Am I missing something ?

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
Berkshelf::BerksfileNotFound: No Berksfile or Berksfile.lock found at: /Users/milosgajdos/berkshelf-playground/getting-started/Berksfile

Vagrantfile:

$script = <<SCRIPT
apt-get update
apt-get upgrade
SCRIPT

Vagrant.configure("2") do |config|
  config.vm.box = "testbox"
  config.vm.provision :shell, :inline => $script 
end
@chulkilee

This comment has been minimized.

Show comment
Hide comment
@lodotek

This comment has been minimized.

Show comment
Hide comment
@lodotek

lodotek Jan 20, 2015

@chulkilee - the link you posted returns a 404.
I am having the same issue as @milosgajdos83 .

lodotek commented Jan 20, 2015

@chulkilee - the link you posted returns a 404.
I am having the same issue as @milosgajdos83 .

@chulkilee

This comment has been minimized.

Show comment
Hide comment
@chulkilee

chulkilee Jan 20, 2015

Contributor

Looks like it is moved to berkshelf/vagrant-berkshelf#6

Contributor

chulkilee commented Jan 20, 2015

Looks like it is moved to berkshelf/vagrant-berkshelf#6

@berkshelf berkshelf locked and limited conversation to collaborators Jun 16, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.