Stuck on "Starting Local Machine" after updating to 2.1.1

Clay? Anyone?? Still unable to open… Thank you to anyone in advance for help!

Hi @JT8888,

It looks like you’re still running into the same issue. The nfs.json file may not be saved correctly.

Here’s a different solution for now:

  1. Open Terminal
  2. Enter sudo nano /etc/exports (enter your password when prompted)
  3. Remove every line
  4. Restart Local

That worked!

Thank you, thank you, thank you Clay!

Stuck on Starting Local Machine.

Running Version 2.0.8 (2.0.8). Can’t update Local.

Tried the fixes listed in this thread. Still not working.

Please advise.

Thanks.

local-by-flywheel.log (157.7 KB)

Hi @gbettant,

Thanks for the log!

Please give Local 2.2.0 (pre-release) a try. It changes how Faster Docker Volumes works.

I just installed Local by Flywheel on a Pc and run into the stalled “Starting Local Machine” problem as well. and I’m on a windows 10 local-by-flywheel.log (112.8 KB)

Hi @Eric_Strickland,

Sorry for the trouble! It looks like your VirtualBox disk needs repaired.

Can you please try running the following in CMD.exe?

"%ProgramFiles%\Oracle\VirtualBox\VBoxManage.exe" internalcommands repairhd "%HomePath%\.docker\machine\machines\local-by-flywheel\disk.vmdk"

i did that sir and i got this: No file format specified and autodetect failed - please specify format: VERR_NOT_SUPPORTED

maybe i didn’t do it right?? you think?

i put this: C:\Users\erics>“ProgramFiles\Oracle\VirtualBox\VBoxManage.exe” internalcommands repairhd “HomePath.docker\machine\machines\local-by-flywheel\disk.vmdk”

man I have no idea what I’m doing!!

No idea if this might help somebody else, but I was able to get Local running again on macOS 10.13.1 (after upgrading to 2.1.2 and getting constant stalled “Starting local machine…”, “Restarting…”) by:

  • Downloading 2.2.0 (pre-release) and just replacing the Local by Flywheel.app file in Applications
  • Doing the “sudo nano /etc/exports” scrub mentioned by @clay here
  • Opening VirtualBox.app
  • Right-clicking local-by-flywheel (which was running even though Local was closed) and Close > Power Off
  • Reopening Local

@Eric_Strickland,

Make sure you copy and paste the command I provided. You can paste into CMD by right-clicking.

After the command shows in CMD, press Enter.

not trying to be mean but did you not really read my comment??? I did what you said to do!! i did this->>> copy & past in cmd . pressed enter with this->>“ProgramFiles\Oracle\VirtualBox\VBoxManage.exe” internalcommands repairhd “HomePath.docker\machine\machines\local-by-flywheel\disk.vmdk”
and
i got this ->>No file format specified and autodetect failed - please specify format: VERR_NOT_SUPPORTED

Can you try running the command again and then screenshot the output in Cmd.exe? I’d like to see the full output if possible.

Hi Clay,

Just installed the latest version of Flywheel. I’d love to use it instead of XAMPP. However, it isn’t working and constantly hangs at Starting Local Machine. Am I supposed to start Virtual Box separately or what? I watched a video of someone using this on a MAC flawlessly. Is this all Windows related? Here’s what the log file says (I’m using Windows 7 Ultimate):

Dec 1, 2017, 5:03 PM EST - info: [main/index] Existing Pressmatic data does not exist.
Dec 1, 2017, 5:03 PM EST - info: [main/check-system] Check System: Docker Machine:
{ stdout: ‘Stopped\n’, stderr: ‘’ }
Dec 1, 2017, 5:03 PM EST - info: [main/docker-machine] Checking Boot2Docker.iso hash
Dec 1, 2017, 5:03 PM EST - info: [renderer/CheckEnvPage] Check system promise response:
[ undefined, ‘machine-halted’ ]
Dec 1, 2017, 5:03 PM EST - info: [main/docker-machine] Boot2Docker.iso hash does not match!
Dec 1, 2017, 5:03 PM EST - info: [main/docker-machine] Copying C:\Users\Owner\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\boot2docker.iso to C:\Users\Owner.docker\machine\machines\local-by-flywheel\boot2docker.iso
Dec 1, 2017, 5:03 PM EST - info: [main/docker-machine] Running C:\Users\Owner\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe start local-by-flywheel
Dec 1, 2017, 5:03 PM EST - info: [main/docker-machine] Starting “local-by-flywheel”…
Dec 1, 2017, 5:03 PM EST - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed…
Dec 1, 2017, 5:03 PM EST - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP…

Hi Robert,

It looks like it’s only been 3 minutes since the Waiting for an IP step. I would recommend giving it a little more time.

How long should it take?

It depends on the computer but I would give it around 10-15 minutes max.