-
Notifications
You must be signed in to change notification settings - Fork 9
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 installation not recognized when installing plugins #133
Comments
After installing vagrant 2.2.4, could you try running those commands from the powershell? |
I think you need to execute the vagrant command in a "regular" windows shell, not a unix shell (like @sarpu is suggesting, I think). I think these commands might help: https://www.isunshare.com/windows-10/4-ways-to-open-command-prompt-in-windows-10.html |
I installed 2.2.4 and ran the vagrant plugin install command from powershell as suggested by @sarpu (not command prompt). There were still some failures in installation |
the installation of the plugins seems to have failed. can you try installing each of the plugins individually, and see which one fails, and maybe see why? the most important one of the three plugins is probably the "vbguest" one, but the others have helped in various situations, too. in your log-file, the system seems to try to install "aws" and fails, and it does not seem to try and install the other ones. the solution to your problem may be in the vagrant documentation, googling turns up e.g. https://www.wordspeak.org/posts/yak-shaving-with-vagrant-travis-ci-and-aws.html - but not sure if this applies to your situation. |
Thanks! I installed the three plugins individually in the following order:
After those installations, I was able to run |
System:
Windows 10 Enterprise
Intel core i5-6300U CPU @ 2.4GHz
RAM usable: 7.89 GB/9 GB
I may be doing something obviously wrong since I don't normally use Windows, but I'm happy for you to tell me what I'm doing wrong here :)
vagrant plugin install vagrant-aws vagrant-sshfs vagrant-vbguest
Here's what I get:
I checked and the files are definitely installed under C/HashiCorp/ so I'm not sure what the disconnect here is. I've tried repairing the Vagrant installation and deleting and reinstalling it. I've tried 2.2.4 and 2.2.5. I've re-started the computer after each change in the Vagrant installation.
Here's what I get when I try to sudo install Vagrant from the terminal, as it recommends in the output (a lot of not-founds and failures to fetch):
Advice?
The text was updated successfully, but these errors were encountered: