Plans for High Sierra support?

Support
22

Ian,

Can you check which version of VirtualBox you’re running? You can find it by going to VirtualBox in the macOS menu and then “About VirtualBox”

23

Looks like: 5.1.30 r118389 (Qt5.6.3)

24

Can you try the following?

  1. Right-click on local-by-flywheel in VirtualBox and go to “Settings…”
  2. Go to Network
  3. Find the Adapter that is attached to “Host-only Adapter” and disable it
  4. Go to VirtualBox » Preferences…
  5. Go to Network
  6. Go to Host-only Networks and delete any Host-only networks that exist (Docker/Vagrant/etc will automatically recreate them)
  7. Open up Terminal.app (or your preferred terminal app)
  8. Enter and run the following command: "/Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine" start local-by-flywheel … If the command results in any errors, please provide them here. Otherwise, re-open Local.
25

Here is the error generated by Terminal:

Starting “local-by-flywheel”…
(local-by-flywheel) Check network to re-create if needed…
(local-by-flywheel) Creating a new host-only adapter produced an error: /usr/local/bin/VBoxManage hostonlyif create failed:
(local-by-flywheel) 0%…
(local-by-flywheel) Progress state: NS_ERROR_FAILURE
(local-by-flywheel) VBoxManage: error: Failed to create the host-only adapter
(local-by-flywheel) VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
(local-by-flywheel) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
(local-by-flywheel) VBoxManage: error: Context: “RTEXITCODE handleCreate(HandlerArg *)” at line 94 of file VBoxManageHostonly.cpp
(local-by-flywheel)
(local-by-flywheel) This is a known VirtualBox bug. Let’s try to recover anyway…
Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue

26

@IanS,

Can you try running the this in Terminal?

sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart

If you get any notices about blocked kernel extensions, be sure to open up System Preferences » Security and allow the one from “Oracle, Inc.”

27

OK was able to restart the virtual machine after allowing an item in system prefs, but I am still seeing the never ending starting local machine in Local by Flywheel.

28

Great, at least we’re getting closer :slight_smile:

Can you provide the log file again now that it’s doing something different?

29

Here are both logs:
logs.zip (21.9 KB)

30

Thanks!

I’m sorry to give you a run-around, but can you try the steps I provided in this reply above again?