Hangs on Starting Local Machine after 2.0.2 update

Support
1

I love the new UI in Local 2.0.2, but I can’t get it to consistently launch. I have several sites, so it’s not feasible for me to just delete the VM and start over. I’ve tried the Reset via VirtualBox a few times, and it makes no difference.

Here’s the log:

Jun 4, 2017, 10:06 AM MST - info: [main/index] Existing Pressmatic data does not exist.
Jun 4, 2017, 10:06 AM MST - info: [main/check-system] Check System: Docker Machine:
{ stdout: ‘Stopped\n’, stderr: ‘’ }
Jun 4, 2017, 10:06 AM MST - info: [renderer/CheckEnvPage] Check system promise response: [ undefined, ‘machine-halted’ ] machine-halted
Jun 4, 2017, 10:06 AM MST - info: [main/docker-machine] Checking Boot2Docker.iso hash
Jun 4, 2017, 10:06 AM MST - info: [main/docker-machine] Running /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Jun 4, 2017, 10:06 AM MST - info: [main/docker-machine] Starting “local-by-flywheel”…
Jun 4, 2017, 10:06 AM MST - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed…
Jun 4, 2017, 10:06 AM MST - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP…
Jun 4, 2017, 10:06 AM MST - info: [main/docker-machine] Machine “local-by-flywheel” was started.
Jun 4, 2017, 10:06 AM MST - info: [main/docker-machine] Waiting for SSH to be available…
Jun 4, 2017, 10:06 AM MST - info: [main/docker-machine] Detecting the provisioner…
Jun 4, 2017, 10:06 AM MST - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the docker-machine env command.

The log ends up pretty much in the same place every time I try to launch.

I’ve not found any other thread that has exactly this issue.

Also, I’m an original Pressmatic user, but I’ve rebuilt all my sites from scratch a couple of times since then. However, there still seems to be some legacy Pressmatic stuff going on as visible in the log.

Please help!

2

Downgrade to Local 2.0.1 by overwriting the current Local 2.0.2 with the Local 2.0.1 app.

Local 2.0.1 works.

1 Like
3

Had the exact same problem and logfile entries @chadbush described, switching back to 2.0.1 made Local alive again, thanks @marianco!

(I have to admit thinking about going back to dumb MAMP Pro or switching to Laravel Valet occasionally – Pressmatic/Local seems to be eating up a lot of my time lately)

2 Likes
4

Thanks! Would you mind pointing me in the direction of a 2.0.1 installer?

5

I found all the releases here
BTW: there might be some Voodoo including starting headless that might make 2.0.2 live again. (Haven’t tried it myself).

6

Yea, same here. I absolutely dread any Local updates now. Right now I’m sitting at VB errors, and a hanging “starting local machine” screen…

7

Releases - Local

8

That did not work for me.
Tried it several times to no avail.

9

Hi all,

Please try 2.0.3. This update includes a fallback for NFS that should resolve this issue. If it doesn’t you can try going to Preferences » Advanced and disabling “Faster Docker Volumes”

See Local by Flywheel 2.0.3 (macOS Only)

10

Thanks Clay! Version 2.0.3. seems solid and so far seems to resolve the problems I was experiencing. And I haven’t yet had to turn off Faster Docker Volumes. And my sites seem much faster.

Great work on the new UI, too!

1 Like
11

Same here, I have wasted more hours this week trying to solve the problem of computer hanging and have lost sites I have created and ABSOLUTELY no help from the program creators.