Bash: Vagrant: Command not found

[Phil Nickols]

Hi all.

This is my first attempt at any kind of VM or Vagrant install.  I have followed a couple of different Vagrant / Homestead guides, but keep failing at the same point.

My issue is that Vagrant is neither conducting 'up' or 'init' or giving a version with '-v'.  Every vagrant command results in a "Bash: Vagrant: Command not found" error.

I firstly figured out I must use the ./ before the vagrant command, but that didn't change the error. I could now use some help understanding what a Vagrant installation should look like in my Win 7 PC, and how to make Git Bash find the right files.

Here's what I have:

- I installed v2.1.2 from vagrantup.org

- It is in the default folder C:\Hashicorp\Vagrant

- C:\Hashicorp\Vagrant has two folders in it: Bin (empty), embedded (many subfolders, with folders such as gems and mingw32)

I suspected a PATH issue, but the only article I could find on stack exchange said I needed to configure a system variable to the C:\Hashicorp\Vagrant\bin folder.  I feel like the bin file should have the Vagrant system in it.

Regardless of what I do, it results in an empty bin folder.   I even used lessmsi to inspect the .msi contents. All files within the msi are directed into embedded folder, none are listed for the bin folder.

So...

- Should Vagrant\bin have files in it?

- Is there somewhere else I should be directing the system variable, so that Git Bash can find vagrant?

- Have I stumbled upon a bug?

Any help appreciated.

Phil

[Antonio]

Hello, I have the same issue. I do not know how to solve it to run globally vagrant on windows 10.

[Phil Nickols]

Vagrant v2.1.2 is missing vagrant.exe in the 32 bit i686.msi

It has been raised as an issue on Github. Without the executable, it, of course, was throws a command not found error. https://github.com/hashicorp/vagrant/issues/10026?_pjax=%23js-repo-pjax-container

V2.1.1 has the correct file.

[Antonio Mateo Hinojo]

ok, thanks. Now I am on vagrant up timed out. What an adventure!!!

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/0e1a2800-48d1-46d5-9159-3594e7301095%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Alvaro Miranda Aguilera]

are you using hashicorp/precise64 ?

if yes

you can do vagrant halt

then open virtualbox gui, and turn on the VM and check the console for errors

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHsJ6JH7XKqT%3DMH%3D1JGL%2BjMYhE8PwNK3bUsC4JfvijHMFeJXgA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro