search

boot2docker / osx-installer

Docker installer for Mac OS X
Apache License 2.0
1.25k stars 258 forks source link

Kernel Panic on Early 2015 Macbook Pro #106

Closed caleblloyd closed 6 years ago

caleblloyd commented 9 years ago

Using the new Early 2015 Macbook Pro (MacBookPro12,1). "boot2docker init" works fine, however when starting using "boot2docker up" or the VirtualBox UI, I get a kernel panic.

VirtualBox Versions tested with problem: 4.3.24, 4.3.22, 4.3.20, all others untested Boot2Docker Versions tested with problem: 1.50, 1.41, all others untested

The kernel extension referenced as the culprit in the kernel panic output is org.virtualbox.kext.VBoxDrv(4.3.24), so I have opened an upstream Virtualbox Ticket (kernel panic log is uploaded there): https://www.virtualbox.org/ticket/13951

Anyone know of a cause or workaround in the meantime?

caleblloyd commented 9 years ago

Workaround is to install Virtualbox 4.3.25 test build. Hopefully this GA's soon and can be integrated in the next boot2docker OSX Launcher release.

SvenDowideit commented 9 years ago

@tianon

Dangeranger commented 9 years ago

Experiencing a similar problem here, link to Gist of panic crash report below. All crashes are based on the bundled VBoxManager (4.3.20) https://gist.github.com/Dangeranger/d5076fd104cd665fdb54

EDIT: virtualbox v.4.26.x fixes the panic crashes

kmadel commented 9 years ago

Updated VBox to 4.3.27 - don't get kernel panic but ssh key set up no longer working and login is required:

..............docker@localhost's password:

algobardo commented 9 years ago

Same here, working if virtualbox is installed after (so that the kext are overriden). However, what is the default password ?

caleblloyd commented 9 years ago

Pretty sure it's "tcuser" (https://github.com/boot2docker/boot2docker/blob/master/README.md)

kmadel commented 9 years ago

I updated to VBox 4.3.27 after doing the Mac OS X install but it appears there is an issue with the VirtualBox Guest Additions not being installed and this appears to be causing an issue with the init. I get the following error on boot2docker -v init:

2015/03/30 12:44:29 executing: VBoxManage storageattach boot2docker-vm --storagectl SATA --port 0 --device 0 --type dvddrive --medium /Users/kmadel/.boot2docker/boot2docker.iso
2015/03/30 12:44:29 executing: VBoxManage storageattach boot2docker-vm --storagectl SATA --port 1 --device 0 --type hdd --medium /Users/kmadel/VirtualBox VMs/boot2docker-vm/boot2docker-vm.vmdk
VBoxManage: error: The medium '/Users/kmadel/VirtualBox VMs/boot2docker-vm/boot2docker-vm.vmdk' can't be used as the requested device type
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Medium, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 178 of file VBoxManageDisk.cpp
VBoxManage: error: Invalid UUID or filename "/Users/kmadel/VirtualBox VMs/boot2docker-vm/boot2docker-vm.vmdk"
error in run: Failed to initialize machine "boot2docker-vm": exit status 1
ghost commented 9 years ago

Guys, I have (probably) workaround for you. I got same error as kmadel. There can't be spaces in path to VirtualBox machines! If you put the path without spaces and run 'boot2docker init' (and 'boot2docker delete' before if exists one), all will be inited well (using VB 4.3.27). Hope it helped.

tianon commented 6 years ago

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).