Boot2docker.iso causing kernel panics with Virtualbox

Hi guys,

Really annoying but with the past few versions of Local. It’s been like this for at least a few months. In short, somewhere along the line the version of boot2docker shipped with Local started breaking my local-by-flywheel VM. My only ‘fix’ is to go into my machine backups and grab a copy of the boot2docker.iso image and replace the one which Local keeps updating.

I’m currently running:

OS: Mojave - 10.14.2
Local: 3.0.4
Virtualbox: 5.2.24 r128163 (Qt5.6.3)

With the default boot2docker.iso file in place, Local hangs waiting for an IP.

Jan 24, 2019, 10:56 AM GMT - info: [main/docker-machine] Checking Boot2Docker.iso hash
Jan 24, 2019, 10:56 AM GMT - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Jan 24, 2019, 10:56 AM GMT - info: [main/docker-machine] Starting "local-by-flywheel"...
Jan 24, 2019, 10:56 AM GMT - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Jan 24, 2019, 10:56 AM GMT - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP...

So I then booted the VM directly in Virtualbox in normal mode so I could see what happens.
I can see a kernel panic happening almost immediately. As soon as I drop in my older boot2docker.iso into ~/.docker/machine/machines/local-by-flywheel and then boot the machine again in normal mode the VM boots with no issues.
I can then load Local and use normally.

But a couple of days later it looks like the .iso file is again replaced by the newer version and I’m back to square one.

Any ideas?

Hey guys - anyone from Flywheel checking the forums lately?

Nothing at all guys??

@ct_roy,

This is very interesting. What version of boot2docker are you downgrading the VM to?

Also, are you running Local 3.0.4?

@clay

Local 3.0.4 (as per original issue report).

Re: boot2docker version - here’s a screenshot of the machine when I boot it manually with the downgraded version


I wasn’t sure it the version number 17.05.0-ce was the boot2docker version or the Docker version number.

My bad! Thanks for clarifying.


Thanks for the screenshot. That’s interesting since it’s quite old (May 2017).

Can you provide a screenshot of the kernel panic by chance?

Sure - see below.
To re-create the panic, I simply tmp renamed my version of boot2docker.iso that works to something like boot2dockerworks.iso - then I open Local, which drops in a fresh copy of boot2docker.iso.
This then sits timing out forever, so I power down the machine in Virtualbox and boot it in normal mode from here - and I see the sshot below:

in my case, what I’ll do now to get back up and running is shut the machine down - drop back in the older boot2docker and boot the machine in Virtualbox, then when I open Local everything works correctly instantly.

any update on this one?

Right - is it safe to assume the lack of any insight on this issue means I’m stuck with it?

If so, I think I’m done with Local - shame :confused: