Yes. Confirming this is how I install Vagrant, and also add plugins. I've used Vagrant for a few years, though not everyday as I do less web development these days than earlier.
I was working on an install last month without any issues. But it's hard for me to know what went wrong and when. I don't know if this helps, but I tried installing Bindler, instead of Vagrant PluginBundler Plugin, and on vagrant up I got this: /Users/Decline/.vagrant.d/gems/2.4.3/gems/bindler-0.1.4/lib/bindler/bend_vagrant.rb:18:in `hook': wrong number of arguments (given 2, expected 1) (ArgumentError) from /opt/vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/environment.rb:162:in `initialize' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.2/bin/vagrant:131:in `new' from /opt/vagrant/embedded/gems/gems/vagrant-2.0.2/bin/vagrant:131:in `<main>' So I uninstalled it and vagrant up works. So far as I can see, no vagrant plugins work for me at present. But I don't know why. On Saturday, February 24, 2018 at 1:01:56 PM UTC+2, Alvaro Miranda Aguilera wrote: > > Hello > > not sure how you install vagrant or plugins > > vagrant is binary distribution, so confirm you download from our webpage > > for plugins, use > > > vagrant plugin install <name of the plugin> > > the plugin usually have vagrant- as prefix > > ie > > vagrant plugin install vagrant-myawesomeplugin > > > Thanks > Alvaro. > > On Fri, Feb 23, 2018 at 11:47 PM, Ian Robert Douglas < > ian.rober...@gmail.com <javascript:>> wrote: > >> Further to my issue (in case it helps anyone to see what is going on >> here): >> >> I ran this command: >> >> mv ~/.vagrant.d ~/.vagrant.d.backup >> >> This allowed vagrant up to work >> >> But the most critical plugin I use is hostupdater, and I guess the >> command above wiped it out. >> >> I reinstalled hostupdater only. >> >> I ran vagrant reload, and it works more or less as expected. >> >> But hostupdater is not being loaded, and if I run bundle show I still get >> the following, everywhere: >> >> Could not locate Gemfile or .bundle/ directory >> >> So, essentially, plugins are broken on my system. >> >> My project (a Wordpress install) is accessible via its IP, but not via a >> custom hostname (i.e., project1.test) >> >> My hosts file is not being updated, obviously. >> >> >> On Friday, February 23, 2018 at 10:47:45 AM UTC+2, Ian Robert Douglas >> wrote: >>> >>> Spent the last day trying to solve this, but I keep hitting a brick wall. >>> >>> I upgraded to Vagrant 2.0.2. >>> >>> OSX 10.13.4 Beta. >>> >>> Virtualbox 5.2.6 r120293 (Qt5.6.3) >>> >>> I have Vagrant installed in the standard way. And a number of projects >>> in individual folders in my User directory. I was trying to set up a new >>> project and I ran into this: >>> >>> Vagrant failed to initialize at a very early stage: >>>> The plugins failed to load properly. The error message given is >>>> shown below. >>>> Could not locate Gemfile or .bundle/ directory >>> >>> >>> I have tried vagrant plugin repair >>> >>> I have tried vagrant plugin expunge --reinstall >>> >>> These are the plugins I have: >>> >>> bundler (1.16.1) >>> hostupdater (1.0.0) >>> vagrant-gatling-rsync (0.9.0) >>> vagrant-plugin-bundler (0.1.1) >>> vagrant-share (1.1.9, system) >>> vagrant-triggers (0.5.3) >>> vagrant-vbguest (0.15.1) >>> >>> When I try vagrant up in my project, I get the error above. >>> >>> I tried uninstalling Vagrant from command line and reinstalling. No >>> difference. >>> >>> I tried downgrading to Vagrant 2.0.1. No difference. >>> >>> I updated Command Line Tools for Xcode, even though I never use any of >>> that. >>> >>> Basically, I have no clue why I cannot get Vagrant to work at all. >>> >>> I searched the web and read everything I could on "Could not locate >>> Gemfile or .bundle/ directory". I'm not finding anything that helps. >>> >>> So I come back here. >>> >>> Can someone point me in the right direction? >>> >>> >>> >>> >>> Thanks in advance for any assistance. >>> >>> best, >>> ian >>> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/vagrant/issues >> IRC: #vagrant on Freenode >> --- >> 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 vagrant-up+...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/525d5a51-a3f4-44f9-a3f8-0afbf6127ade%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/525d5a51-a3f4-44f9-a3f8-0afbf6127ade%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Alvaro > > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- 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 vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/783b699e-1012-4cca-b741-23debb5dcd3f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
