0

Looking for some assistance with Vagrant, for what I believe is a Server Variable issue.

I have been trying all weekend to get any kind of Vagrant install up and running. I have followed: Laravel Homestead installation guide, and Sitepoint Homestead Vagrant VM guide.

I am using the default folders for install. Whatever I do, after installing Vagrant, I am unable to run 'vagrant up' or vagrant init' because the command 'vagrant' cannot be found (bash: vagrant: command not found). I am trying to execute from the folder with Vagrantfile in it, as suggested by Sitepoint.

I found this Stack Overflow article: Vagrant Command Stopped Working: Command not Found on Windows, but with the current version doesn't work as that bin folder is empty (note that the 'embedded' folder beside it is full, with several 'bin' folders down within the subfolder structure).

I am not familiar enough with Vagrant to know to which folder I should set the server variable, if indeed that is the right answer. It has to be simple, as no sites address this particular issue anywhere. Any assistance will be greatly appreciated.

Win 7, Vagrant 2.1.2, Virtualbox 5.2.14

Phil
  • 11
  • 1
  • 2
  • does vagrant --version display the version ?? if not then there is an installation issue – rohit thomas Jul 09 '18 at 05:05
  • Nope. Same issue as all the others, command not found.Thanks for that though... Does it matter what folder I run the command from? – Phil Jul 09 '18 at 09:51
  • I think you have done a mistake when downloading Vagrant 2.1.2, it does have a bin folder where did you download it from ?? did you try the official site https://www.vagrantup.com/downloads.html ?? – rohit thomas Jul 09 '18 at 11:23
  • absolutely used vagrantup.com – Phil Jul 09 '18 at 11:35
  • So I just checked inside the msi file, using lessmsi. Every single file in the msi package is sent to the embedded folder (or one of its subfolders) as the destination. – Phil Jul 09 '18 at 11:57
  • I just downloaded the version 2.1.2 and I can assure you that there is in fact a folder called bin at this location `C:/HashiCorp/Vagrant/bin` i.e. in the installation directory – rohit thomas Jul 10 '18 at 02:26
  • I agree. But what's in it? I have nothing. – Phil Jul 10 '18 at 12:07
  • Update: I navigated into my vagrant folders, found an executable called vagrant, and tried to run it. Again - Bash: Vagrant: Command not found. Git Bash wouldn't execute a file right in front of it. Answer to that part is to put ./ in front of the filename. First issue solved, thanks to this post: – Phil Jul 10 '18 at 12:36
  • [Why can't Git Bash Run My Executable?](https://stackoverflow.com/questions/29805173/why-cant-git-bash-run-my-executable) Still have path issues, it's searching for Ruby way down in this folder: C:/Users/vagrant/AppData/Local/Temp/4aksidm5.fmu/embedded/mingw32/bin/ruby.exe: bad interpreter: No such file or directory – Phil Jul 10 '18 at 12:46
  • Don't run it directly :P and yes the `vagrant.exe` is located in the bin folder ...Anyway now add this .exe file into your env variables like mention here https://stackoverflow.com/questions/35655038/vagrant-command-stopped-working-command-not-found-on-windows.... now in your cmd type `vagrant -v` ...should work now :) – rohit thomas Jul 11 '18 at 02:34

1 Answers1

1

At the time of writing, Vagrant v2.1.2 is missing vagrant.exe in the i686.msi file.

There are two parts to this answer.

Thanks for your support Rohit.

Phil
  • 11
  • 1
  • 2