I moved the software to a new computer, and now WebODM won’t start. I have followed the trouble-shooting guide, uninstalled and reinstalled, etc. After three reboots following the guide, still no joy. Any suggestions from the SMEs?
Frustrating that something I payed for won’t work.
Console output:
Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
Detected OS with VirtualBox support
Initializing console…
Checking for OpenSSH Client at C:\Windows\system32\OpenSSH\ssh.exe
OpenSSH check passed
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
No default docker-machine, good!
Docker machine “webodm” does not exist. Use “docker-machine ls” to list machines. Use “docker-machine create” to add a new one.
Docker is not communicating properly. We’ll attempt to establish communication…
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
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 --virtualbox-no-vtx-check --driver virtualbox --virtualbox-disk-size “124000” --virtualbox-memory “4774” --virtualbox-cpu-count “4” webodm
Creating CA: C:\docker-webodm\certs\ca.pem
Creating client certificate: C:\docker-webodm\certs\cert.pem
Running pre-create checks…
(webodm) Image cache directory does not exist, creating it at C:\docker-webodm\cache…
(webodm) No default Boot2Docker ISO found locally, downloading the latest release…
(webodm) Latest release for github.com/boot2docker/boot2docker is v19.03.5
(webodm) Downloading C:\docker-webodm\cache\boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v19.03.5/boot2docker.iso…
(webodm) 0%…10%…20%…30%…40%…50%…60%…70%…80%…90%…100%
Creating machine…
(webodm) Copying C:\docker-webodm\cache\boot2docker.iso to C:\docker-webodm\machines\webodm\boot2docker.iso…
(webodm) Creating VirtualBox VM…
(webodm) Creating SSH key…
(webodm) Starting the VM…
(webodm) Check network to re-create if needed…
(webodm) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the taskbar.
Error creating machine: Error in driver during machine creation: Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm webodm --type headless failed:
VBoxManage.exe: error: The virtual machine ‘webodm’ has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in ‘C:\docker-webodm\machines\webodm\webodm\Logs\VBoxHardening.log’
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
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.
usually a “hardening” issue with VirtualBox is caused due to third party software (perhaps an antivirus?) interfering with the VM startup.