The initialization failed. Could not create virtual machine. Restart the application. While in the console report the problem as:
Detected Windows 10 with Hyper-V support
Initializing console…
Checking Hyper-V status…
Hyper-V is enabled
‘docker-machine’ is not recognized as an internal or external command,
operable program or batch file.
Docker is not communicating properly. We’ll attempt to establish communication…
‘docker-machine’ is not recognized as an internal or external command,
operable program or batch file.
Checking for VM Switch…
Found WebODMSwitch
WebODM VM does not exist. We’re going to create it now… hang on tight! If this takes more than 10 minutes, please try restarting your computer.
create --driver hyperv --hyperv-disk-size “535000” --hyperv-memory “17572” --hyperv-cpu-count “4” --hyperv-virtual-switch “WebODMSwitch” webodm
Uh oh! Check the console. Check that you have enough memory available, disk space, that your firewall is off and that you have restarted your computer. Refer to the troubleshooting section of the installation manual for more information.
‘docker-machine’ is not recognized as an internal or external command,
operable program or batch file.
Hey @chhengngunn, for some reason it looks like a required component (docker-compose) did not install properly during setup. Could you try to install it manually https://download.docker.com/win/stable/Docker%20for%20Windows%20Installer.exe, then restart WebODM Manager?
The new works station was setup. But, might another problem as console reporting as:
Hyper-V Requirements: VM Monitor Mode Extensions: Yes
Detected Windows 10 with Hyper-V support
Initializing console…
Checking Hyper-V status…
Hyper-V is enabled
Checking for firewall rules…
Docker is not communicating properly. We’ll attempt to establish communication…
Checking for VM Switch…
Found WebODMSwitch
WebODM VM does not exist. We’re going to create it now… hang on tight! If this takes more than 10 minutes, please try restarting your computer.
create --driver hyperv --hyperv-disk-size “535000” --hyperv-memory “17572” --hyperv-cpu-count “4” --hyperv-virtual-switch “WebODMSwitch” webodm
Running pre-create checks…
(webodm) No default Boot2Docker ISO found locally, downloading the latest release…
(webodm) Latest release for GitHub - boot2docker/boot2docker: DEPRECATED; see https://github.com/boot2docker/boot2docker/pull/1408 is v18.03.0-ce
(webodm) Downloading E:\docker-webodm\cache\boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v18.03.0-ce/boot2docker.iso…
(webodm) 0%…10%…20%…30%…40%…50%.Error removing file: Error removing temporary download file: remove E:\docker-webodm\cache\boot2docker.iso.tmp475222359: The process cannot access the file because it is being used by another process.
(webodm)
Error with pre-create check: “read tcp 10.4.178.119:49952->52.216.160.3:443: wsarecv: An existing connection was forcibly closed by the remote host.”
Uh oh! Check the console. Check that you have enough memory available, disk space, that your firewall is off and that you have restarted your computer. Refer to the troubleshooting section of the installation manual for more information.
Try pressing the “Delete VM” from the maintenance panel, then restart your computer and rerun WebODM Manager.
Actually, I tried following instruction as you comment by deletet virtual machine and restarted the WebODM. I also check the Hyper-V management and connect to the virtual marching. But still appear the same error problem!
Mm, the error message that stands out to me is:
Error removing file: Error removing temporary download file: remove E:\docker-webodm\cache\boot2docker.iso.tmp475222359: The process cannot access the file because it is being used by another process.
It implies that something else is currently trying to read the file… have you disabled all antiviruses?