Met a W10 user at Meetup whose Local-by-Flywheel is working.
I have tried reloading repeatedly with variations - not working.
Am I the only W10 user failing? If so, any solutions or even clues??? Thanks - I hope.
Log file below:
Jan 19, 2018, 8:59 AM PST - info: [main/index] Existing Pressmatic data does not exist.
Jan 19, 2018, 8:59 AM PST - info: [main/check-system] Check System: Docker Machine:
{ stdout: ‘Stopped\n’, stderr: ‘’ }
Jan 19, 2018, 8:59 AM PST - info: [renderer/CheckEnvPage] Check system promise response:
[ undefined, ‘machine-halted’ ]
Jan 19, 2018, 8:59 AM PST - info: [main/docker-machine] Checking Boot2Docker.iso hash
Jan 19, 2018, 8:59 AM PST - info: [main/docker-machine] Boot2Docker.iso hash does not match!
Jan 19, 2018, 8:59 AM PST - info: [main/docker-machine] Copying C:\Users\ALBERT WALTNER\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\boot2docker.iso to C:\Users\ALBERT WALTNER.docker\machine\machines\local-by-flywheel\boot2docker.iso
Jan 19, 2018, 8:59 AM PST - info: [main/docker-machine] Running C:\Users\ALBERT WALTNER\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe start local-by-flywheel
Jan 19, 2018, 8:59 AM PST - info: [main/docker-machine] Starting “local-by-flywheel”…
Jan 19, 2018, 8:59 AM PST - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed…
Jan 19, 2018, 8:59 AM PST - info: [main/docker-machine] (local-by-flywheel) Windows might ask for the permission to create a network adapter. Sometimes, such confirmation window is minimized in the taskbar.
Jan 19, 2018, 9:01 AM PST - info: [main/docker-machine] (local-by-flywheel) Creating a new host-only adapter produced an error: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe hostonlyif create failed:
Jan 19, 2018, 9:01 AM PST - info: [main/docker-machine] (local-by-flywheel) 0%…
Jan 19, 2018, 9:01 AM PST - info: [main/docker-machine] (local-by-flywheel) Progress state: E_FAIL
Jan 19, 2018, 9:01 AM PST - info: [main/docker-machine] (local-by-flywheel) VBoxManage.exe: error: Failed to create the host-only adapter
Jan 19, 2018, 9:01 AM PST - info: [main/docker-machine] (local-by-flywheel) VBoxManage.exe: error: Querying NetCfgInstanceId failed (0x00000002)
Jan 19, 2018, 9:01 AM PST - info: [main/docker-machine] (local-by-flywheel) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
Jan 19, 2018, 9:01 AM PST - info: [main/docker-machine] (local-by-flywheel) VBoxManage.exe: error: Context: “enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)” at line 94 of file VBoxManageHostonly.cpp
Jan 19, 2018, 9:01 AM PST - info: [main/docker-machine] (local-by-flywheel)
Jan 19, 2018, 9:01 AM PST - info: [main/docker-machine] (local-by-flywheel) This is a known VirtualBox bug. Let’s try to recover anyway…
Jan 19, 2018, 9:01 AM PST - warn: [main/docker-machine] 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