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.
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 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
I ran into an error after installing VMware Fusion on my mac, that it couldn't find /dev/vmmon. After some digging, I've learned that there are only so many available character devices, and that other software I have has consumed them.
Since I actively use Viscosity and Virtualbox (for the time being), the only other one that I could find I had was Intel HAXM driver.
Instructions online suggest to run a script to uninstall it, however that script did not exist on my laptop.
I unloaded the driver with the command:
sudo kextunload -b com.intel.kext.intelhaxm
I wanted to determine if there is anything else I need to do, will this driver attempt to reload during boot?
Thanks!
The Intel HAXM docs show that as of 2018, there is an uninstall script:
sudo /Library/Extensions/intelhaxm.kext/Contents/Resources/uninstall.sh
I had the same issue, Tim Potter's solution fixed my issue ,
sudo kextunload -b com.intel.kext.intelhaxm
Thanks
Cannot find /dev/vmmon (VMware Fusion 8.5.1 on macOS 10.12.1)
I had the same problem.
After a lot of trial and error, and helpful support from VMware I got it to work by
Create another user on the mac
log in as that new user
start fusion
create a new virtual machine (custom, windows7, no actual OS installation)
If machine starts, then vmmon is restored correctly
switch back to your normal user, start fusion and your existing vm
I have not investigated WHY this works, and VMware-support couldn´t tell me either. For now - I do not care. It works, and I can run my vms again.
I installed RHEL 6.4 server under Parallels 7 on my Mac OS 10.8 just now from an iso file I just downloaded from RedHat. The installation seemed to proceed ok, but at the end I'm left with a screen with a gray bar followed by the text "RedHat Enterprise Linux Server 6.4" with no obvious way how to login.
If I shut down the machine I see it running the shutdown scripts. If I boot it I see the boot scripts and they all look ok. But I always end up at that same screen with no way to login.
I can enter characters in the screen, but there is no Linux prompt at all.
Anybody know what to do next? I couldn't glean anything fro the RedHat install manual.
Thanks,
doug
I had the same problem. The issue is the X-win server will not start because Parallels tools breaks the framebuffer with the RHEL 6.4 update. This is especially easy to see because a fresh install works fine until you install Parallels tools.
When you see the "select system to boot" message, hit the key that allows you to edit the boot arguments. Add a "3" to the end to force the startup to runlevel 3 (which is a console login without the GUI).
After logging in, type the command "starts" and you will see that it fails. Once you are able to fix this problem, the normal bootup into the GUI login will also work.
I had to downgrade the video driver subsystem back to 6.3 for it to start working, and you also have to add an exclusion to yum to prevent it from updating and removing the fix. This will be necessary until Parallels releases an updated tools that addresses this issue. There is a procedure I found in the CentOS forums for how to do this, sorry I don't have the link.