Stuck at 'Starting Local Machine'

Support
1

Hello,

Just upgrade to Windows 10 and I’m stuck at ‘Starting Local Machine’. I’ve read the other support threads on this topic I could find and followed advice here but no luck, I can’t get Local up and running.

Here is my local log… get’s stuck at Waiting for an IP.

C:\Users\ABallard\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-2\out\environment.js
Jun 4, 2019, 9:59 AM GMT+10 - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\ABallard\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-2\out\environment.js
Jun 4, 2019, 9:59 AM GMT+10 - info: [main/check-system] Check System: Docker Machine:
{ stdout: ‘Stopped\n’, stderr: ‘’ }
Jun 4, 2019, 9:59 AM GMT+10 - info: [renderer/CheckEnvPage] Check system promise response:
[ undefined, ‘machine-halted’ ]
Jun 4, 2019, 9:59 AM GMT+10 - info: [main/docker-machine] Checking Boot2Docker.iso hash
Jun 4, 2019, 9:59 AM GMT+10 - info: [main/docker-machine] Running C:\Users\ABallard\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe start local-by-flywheel
Jun 4, 2019, 9:59 AM GMT+10 - info: [main/docker-machine] Starting “local-by-flywheel”…
Jun 4, 2019, 9:59 AM GMT+10 - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed…
Jun 4, 2019, 9:59 AM GMT+10 - info: [main/docker-machine] (local-by-flywheel) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the taskbar.
Jun 4, 2019, 9:59 AM GMT+10 - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP…

Any ideas what to try next?

2

Update: Got this working!

Here’s how I fixed this on Windows 10.

  1. Opened up VirtualBox, right clicked on the local-by-flywheel machine, and selected ‘Show in Explorer’.

  2. Went back to the main machines folder "C:\Users\USERACCOUNT.docker\machine\machines

  3. Renamed the current folder to add “-old”

Started Local again, it creates a new machine and all works as normal.

3

This topic was automatically closed 12 hours after the last reply. New replies are no longer allowed.