I'm running windows 10 Home on a box, have virtualbox installed and vagrant starting VMs. Do you just need to specify the provider for vagrant?
On Sat, May 23, 2020 at 5:03 AM Alvaro Miranda Aguilera <kiki...@gmail.com> wrote: > So, hyper-v network is different from what virtualbox does, so i am not > sure the project will be useful just changing hyper-v where it was > virtualbox > > what you can try is either create a VM or use WSL2 linux > > and replace this line > > force_host_vm = TRUE > > to > force_host_vm = FALSE > > And if you run vagrant from a linux machine, it should just create the > docker containers without the need to create a linux vm. > > i would start there > > once you get there, my suggestion will be invest some time slowly > > create a vagrant project that create a linux vm on hyperv > add a docker container > port this project to your own install > > but if you have time constraints, run this from a linux box should be the > faster path. > > alvaro > > On Fri, May 22, 2020 at 8:46 PM Frank Gunseor <fdav...@gunseor.com> wrote: > >> Hello everyone, >> >> I am relatively new to Vagrant and Docker. >> >> I have the above Vagrantfile(s) running on a Linux OS on my laptop just >> fine. >> >> I would like to get it running on my Windows 10 desktop system due to >> more RAM and faster CPUs. >> >> It appears to me that my problem is that the box(es) related to this >> multi-container, multi-VM system are specific to VirtualBox. >> >> VirtualBox does not function (yet?) on Windows 10 because Docker requires >> Hyper-V to be enabled for it to functional, although VirtualBox claims >> built-in functionality with Hyper-V the consensus on the forums, support, >> etc. and that I can confirm is not ready, yet. >> >> Sooooo, I would appreciate any help that anyone can provide to help me >> get this "system" to run on Widows 10. >> >> Please note that Docker and Vagrant BOTH are running just fine on my >> Windows 10 desktop. >> >> This is the error message I get that is basically the same for every >> container and VM: >> >> An error occurred while executing the action on the 'dev' >> machine. Please handle this error then try again: >> >> There was an error while executing `VBoxManage`, a CLI used by Vagrant >> for controlling VirtualBox. The command and stderr is shown below. >> >> Command: ["startvm", "b8d0a299-220a-4a52-b6c0-4c967ed980d5", "--type", >> "headless"] >> >> Stderr: VBoxManage.exe: error: WHvCapabilityCodeHypervisorPresent is >> FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' >> feature. (VERR_NEM_NOT_AVAILABLE). >> VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX) >> VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component >> ConsoleWrap, interface IConsole >> >> I can provide much more if needed. >> >> Is there anyway to add the Hyper-V provider to this box? If so, how? >> >> Any help is appreciated. >> >> Frank Gunseor >> >> -- >> 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/hashicorp/vagrant/issues >> Discuss: https://discuss.hashicorp.com/c/vagrant/24 >> --- >> 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/b40507a2-8a4f-415b-a471-d3192b936a5b%40googlegroups.com >> <https://groups.google.com/d/msgid/vagrant-up/b40507a2-8a4f-415b-a471-d3192b936a5b%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > 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/hashicorp/vagrant/issues > Discuss: https://discuss.hashicorp.com/c/vagrant/24 > --- > 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/CAHqq0exGw%2BrWKgKey-Z_ooC4XcG4F-u42ML4bxcGK9Ca8Coo2w%40mail.gmail.com > <https://groups.google.com/d/msgid/vagrant-up/CAHqq0exGw%2BrWKgKey-Z_ooC4XcG4F-u42ML4bxcGK9Ca8Coo2w%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/hashicorp/vagrant/issues Discuss: https://discuss.hashicorp.com/c/vagrant/24 --- 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/CA%2B1bPC0xf7GAidGU8-4%3D8pa47%2BtjvF0uxL8HggbrOumCZOxYUg%40mail.gmail.com.
