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 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?