I found this thread when hitting some issues with developing against the Fusion provider. Here's the Gemfile I ended up with:
https://github.com/scalefactory/vagrant-cucumber/blob/master/Gemfile I hope it helps a fellow Google searcher. Note still that the Ruby version you're using with Bundler needs to match that provided by the installer (or, at least, for which there's an RGLoader target). On Wednesday, January 22, 2014 1:54:08 PM UTC, Jimmy Cuadra wrote: > > Solved my own problem again... sorry for all the messages. >_< > > I looked at /Applications/Vagrant/embedded/rgloader/loader.rb, and it > turns out that it requires loaders specific to version of Ruby you're > using. I have Ruby 2.1.0 installed globally, which apparently is not the > same version the officially installed Vagrant uses. Switching to Ruby 2.0 > made it load correctly! > > Hopefully some of the issues I've run into here will be useful in > documenting how to do this. > > On Wednesday, January 22, 2014 5:46:06 AM UTC-8, Jimmy Cuadra wrote: >> >> I just searched the Vagrant source code and discovered that the >> environment variable is named VAGRANT_INSTALLER_EMBEDDED_DIR. Setting that >> resulted in a new error message: >> >> Message: The RubyEncoder loader is not installed. Please visit the >> http://www.rubyencoder.com/loaders/ RubyEncoder site to download the >> required loader for 'darwin' and unpack it into >> '/Applications/Vagrant/embedded/rgloader' directory to run this protected >> script. >> >> >> However, RubyEncoder already exists at >> /Applications/Vagrant/embedded/rgloader. Is there something else I need to >> do to get the bundled Vagrant to recognize it? Thanks! >> >> On Wednesday, January 22, 2014 5:40:07 AM UTC-8, Jimmy Cuadra wrote: >>> >>> Hi Mitchell, thanks for the reply. >>> >>> I tried setting the environment variable, but still got the error >>> message about encoded files being read outside the installer. Is this the >>> correct invocation? >>> >>> $ VAGRANT_EMBEDDED_DIR=/Applications/Vagrant/embedded bundle exec >>> vagrant status >>> Vagrant appears to be running in a Bundler environment. Plugins >>> will not be loaded and plugin commands are disabled. >>> >>> Vagrant failed to initialize at a very early stage: >>> >>> There was an error loading a Vagrantfile. The file being loaded >>> and the error message are shown below. This is usually caused by >>> a syntax error. >>> >>> Path: /Users/jimmy/Code/vagrant-librarian-chef/Vagrantfile >>> Message: Encoded files can't be read outside of the Vagrant installer. >>> >>> >>> I have vagrant-vmware-fusion in the Gemfile, as well as installed to the >>> official copy of Vagrant in /Applications. >>> >>> On Saturday, January 18, 2014 9:15:01 AM UTC-8, Mitchell Hashimoto wrote: >>>> >>>> Jimmy, >>>> >>>> I plan on documenting this, but you'll need a version of Vagrant >>>> installed from the installer, then you need to set the environmental >>>> variable `VAGRANT_EMBEDDED_DIR` I believe to be the "embedded" directory >>>> within that install path... >>>> >>>> >>>> On Wed, Jan 15, 2014 at 11:31 PM, Jimmy Cuadra <[email protected]>wrote: >>>> >>>>> Thanks for the reply. Unfortunately, that doesn't solve the issue for >>>>> me. Adding the dependency to the gemspec is not really different from >>>>> having it in the Gemfile. In both cases, vagrant-vmware-fusion is not >>>>> detected unless I add `require 'vagrant-vmware-fusion'` to my >>>>> Vagrantfile, >>>>> which results in the error message, "Encoded files can't be read outside >>>>> of >>>>> the Vagrant installer." >>>>> >>>>> How can the VMware provider be loaded and licensed in the development >>>>> environment? >>>>> >>>>> >>>>> On Wednesday, January 15, 2014 12:48:48 AM UTC-8, Cassiano Leal wrote: >>>>> >>>>>> You have to add it to you .gemspec file as a development dependency. >>>>>> >>>>>> Check here [0] for an example. >>>>>> >>>>>> After that, do a bundle install and you're done! >>>>>> >>>>>> [0] https://github.com/cassianoleal/vagrant-butcher/ >>>>>> blob/master/vagrant-butcher.gemspec#L23-L25 >>>>>> >>>>>> >>>>>> On 15 January 2014 07:41, Jimmy Cuadra <[email protected]> wrote: >>>>>> >>>>>>> Hello Vagrant users, >>>>>>> >>>>>>> When developing a Vagrant plugin, how do you get Vagrant to >>>>>>> recognize a VMware provider plugin? I'm trying to test my plugin with >>>>>>> *vagrant-vmware-fusion* and not sure how to do it. If I run `bundle >>>>>>> exec vagrant plugin install vagrant-vmware-fusion`, I get an error >>>>>>> message >>>>>>> saying that the `vagrant plugin` command can't be run in a Bundler >>>>>>> environment. If I add the provider plugin to my Gemfile, then running a >>>>>>> `vagrant` command results in the error message, "The provider >>>>>>> 'vmware_fusion' could not be found, but was requested to back the >>>>>>> machine >>>>>>> 'default'. Please use a provider that exists." If I add >>>>>>> `Vagrant.require_plugin "vagrant-vmware-fusion"` to the Vagrantfile, >>>>>>> then >>>>>>> running a `vagrant` command results in the error message, "Vagrant >>>>>>> failed >>>>>>> to initialize at a very early stage: Failed to load the >>>>>>> "vagrant-vmware-fusion" plugin. View logs for more details." Wat do? >>>>>>> Thanks >>>>>>> in advance. >>>>>>> >>>>>>> Jimmy >>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Vagrant" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to [email protected]. >>>>>>> >>>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>>> >>>>>> >>>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Vagrant" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>> >>>> -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
