-
-
Notifications
You must be signed in to change notification settings - Fork 642
Windows 10 enterprise vagrant up #1371
Comments
@ikit-claw - Interesting... Do you have VirtualBox installed on Windows? I haven't run into this before. |
Also, does it say that after you do See potentially related Vagrant issue: hashicorp/vagrant#5189 |
I'm running VMware12 |
Ah, if you want to use Vagrant with VMware, you also have to buy and install the (This is why I've stopped using VMware for my own environments... after three times paying for upgrades to VMware + Vagrant's plugin, I decided it's not worth the effort/price). Otherwise, if you install VirtualBox, Vagrant will detect it's present and work with it instead of VMware. |
So if I go back to using VirtualBox it should work? |
I guess you should put that in the notes. |
Now I get couldn't open base |
Hmm, what's the exact error message? Is it something like #672 |
Okay I followed the suggestions in 672 and it worked played with it a little but today it won't load at all. Why do people use windows argh |
Haha... but to that point: Developing with VirtualBox and Vagrant on Windows. What messages are you getting when it's not loading? Can you grab a screenshot of the console or somehow copy out the text? Also, one other question—what terminal/CLI emulator are you using? I've had the best luck with Cmder or Cygwin, though Powershell and plain old Git Bash may work in some cases too. |
Sorry I've just uninstalled it for now. It was supposed to be a quick thing for a tutorial I might circle back around to this later when I have time to get into it. |
Issue Type
Your Environment
The provider 'PROVIDER' could not be found, but was requested to
back the machine 'default'. Please use a provider that exists.
When running vagrant up prompted to run vagrant up --provider=PROVIDER
The text was updated successfully, but these errors were encountered: