Closed benlwong closed 6 years ago
Not sure what the difference is, but I initiate Boot2Docker manually in a terminal and it ran without a problem (per the Docker documentation):
$ boot2docker init $ boot2docker start $ export DOCKER_HOST=tcp://$(boot2docker ip 2>/dev/null):2375
More than happy to provide any log files or info if it helps track down this potential bug. Ben
Okay, I have more info and can replicate the problem now. Basically, if I am running a virtual machine in Parallels 8 (build 8.0.18619) and I try to start boot2docker, the machine crashes.
If I am running boot2docker, and then try to bring up a VM in Parallels, the machine crashes. I am guessing Parallels is using VirtualBox too? In any case, on my box, I CANNOT run both at the same time. As long as one is running, bringing up the other will crash my system.
yes, all the visualization platforms don't seem to play nicely with each other - Parallels is a different codebase - it might be useful to the world to report the bug to both Parallels and VirtualBox - you never know, it might even get fixed :)
This is mostly to do with VirtualBox. You can't run both VB and Parallels at the same time, as I am not mistaken, VB or Parallels try to exclusively own the hypervisor. Some users might find it lucky to have VMWare Fusion to work together with VB, but not VB with Parallels.
Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).
Running OSX 10.9.3. Downloaded and installed v1.0.0 today fine. But when I run boot2docker for the first time, it brought up my terminal, a bunch of messages flew by, and my system literally crashed. I am not sure where the log file is, but more than happy to provide it if someone points me in the right direction.
I have never installed docker before today.
Thanks, Ben