I am currently attempting to run a macOS High Sierra VM on my Windows 10 laptop using VMWare Workstation 12 Player.
To make the VM work, it says I must disable Hyper-V - Upon disabling, the VM does indeed work.
However, when I want to run Docker on my macOSHS VM, it gives the error:
There is also a link to a page telling one how to work with Hyper-V and that it should be re-toggled to work, along with some CMD code that I can't seem to get to work...
When I turn off Hyper-V the VM starts as normal, but when I try to install/run Docker on there... I am greeted with:
Has anybody run into this problem before?
Follow this answer, basically you have to enable virtualization in the vmware settings in the processor tab.
https://serverfault.com/questions/841330/docker-on-mac-on-vmware/849836#849836
Related
I'm on windows 10 and I'm encountering Docker on Windows crashing on startup.
I just installed docker on windows and have a couple of containers spinning up (last night). I've been able to use it but after reboot, or shutdown, this was the behaviour ever since. Pretty unstable.
It looks like this and terminates after a while without any prompt of an error.
More info that I have Hyper-V installed on my machine and "Use the WSL 2 based engine" option enabled on docker.
On my end, I was able to solve this by:
Going to Apps & Features
Search for Ubuntu (or any linux distro you've installed)
Click on it and navigate to Advance options
Click on Reset button.
Also, try to trial and error which docker on windows version is stable with your system.
Hope that helps.
Windows 10 N Pro, version 2004
I had a few different OS VM's setup before I decided to try Docker out.
After installing it and realizing I better stick to VM's I went on my Virtualbox, tried starting my old VM's and couldn't get past the boot screen - the issue is it goes to a black screen.
I created a few new VM's all resulting in the same issue. I tried restarting the machine, Windows Restore, trying different BIOS settings, uninstalling docker, reinstalling Virtualbox, increasing VRAM to 128MB, uninstalling subsystem for Linux, disabling the Hypervisor and sandboxing. The only thing that let me interact with the VM was enabling EFI - although after choosing "boot" option I had the same black screen.
After trying all possible solutions on SO and Google I stumbled upon a comment (which unfortunately I can't find) which pinpointed that Docker installer explicitly overwrites VM/Hypoer registries or processes. I don't know if that's the issue however it is the case.
How can I get my VM's running again without reinstalling Windows?
It sounds like the problem is: 1) You were successfully running VMs with VirtualBox on Windows 10 Pro, 2) You installed Docker, 3) Docker broke VBox. Correct?
Look here:
https://superuser.com/questions/1290051/virtualbox-no-longer-works-after-uninstalling-docker-on-windows-10.
Control Panel -> Programs and Features
On the left side choose "Turn Windows features on or off
Uncheck Hyper-V
reboot
After reboot you have to reinstall/repair your installation of VirtualBox with the original installer!
Reboot again and it should work 🙂
In general, please try posting these kinds of questions on https://serverfault.com or https://superuser.com. StackOverflow is for "programming" questions.
I've installed docker on windows 10 machine. When I start it I get error
As it can be seen on the picture below, I have Hyper-V switched on as on in the windows features, so not sure what is wrong. Anyone can advise please?
I am not sure about the issue. I did face same issue on my desktop than I switched from Hyper-V to WSL 2. and it worked. Below link could be useful for you.
Docker for Windows-WSL
I recently got a new MacBook Pro running OS X 10.10.2, and I installed Boot2Docker 1.5.0 on it. Aside from Chrome, this is the first program I installed on my new machine. However, when I try to run it, the terminal window opens up for a few seconds, saying boot2docker is up, and then my computer restarts automatically.
I tried to uninstall 1.5.0 and install 1.4.1 (as that is what I was using on my last machine), but I encountered the same problem.
The last thing I see before my laptop restarts is the second image, and the error report my computer shows after the restart is the first image here:
http://i.imgur.com/6TD0Jt6.png
Has anyone every had this problem before, or know how I can address it? Thanks!
Instead of using Boot2Docker, have you considered making a linux virtual machine on your mac? Then you would just run docker on the virtual machine.
This fixed all of the problems I had with boot2docker.
The point of boot2docker is to enable docker to run on your mac. If you use a linux VM you will no longer need boot2docker.
I posted this question in AskDifferent as well, and it turns out there was a problem with OS X Security Update 2015-003 and boot2docker/virtualbox, as per this link: https://github.com/boot2docker/boot2docker/issues/800
Updating my version of VirtualBox remedied the situation.
After a recent update of my OS from Windows 8 to Windows 8.1 my vagrant setup has stopped working.
I try running vagrant up on boxes and I get the following:
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it to boot Valid states are 'starting, running'. The machine is in the 'poweroff' state. Please verify everything is configured properly and try again.
I've tried updating vagrant. I've updated VirtualBox to 4.3. I've tried specifically setting VirtualBox to run as Administrator and in compatibility mode for Windows 8. That didn't work. Also tried compatibility mode for Windows 7. No dice.
Anyone else having these problems? Windows 8.1 is to new to find reports of this through Google searching. hopefully someone here can help out.
So, here is how I actually managed to fix it.
The newest versions of Vagrant (1.3.5) and VirtualBox (4.3.4) do not play together at all on Windows. So, I kept Vagrant 1.3.5 and went down to VirtualBox 4.2.2.
Once you have that, you have to get rid of a couple folders so that everything resets itself correctly:
Users\<<USERNAME>>\.VirtualBox
Users\<<USERNAME>>\.vagrant.d
Delete those before trying to run
vagrant up
With that, I was able to get everything running again. However, I have noticed that running vagrant up does go a tad slower than it had been previously. I can live with that though.
Thank you for all of your help and suggestions.
Ran into this problem and figured out the problem. Turns out I did not have the proper virtualization settings enabled in my bios.
Vagrant emitted a helpful error:
If the provider you're using has a GUI that comes with it, it is often
helpful to open that and watch the machine, since the GUI often has
more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run vagrant up while the
VirtualBox GUI is open.
Followed the instructions and tried to power on the vm via the GUI and was greeted with this error:
Was able to vagrant up after turning on the proper settings in my bios.
OS: Windows 8.1, Vagrant version: 1.3.5, Virtual Box version: 4.3.4
opening VirtualBox GUI may give you a better idea of what's going on. 4.3 has been recently released, so if you've updated, your issue may be related to that
Running Vagrant on Windows 8.1 has caused Windows 8.1 to reboot shortly after a vagrant up for me. I am able to recreate this every time.