Docker: Looks something went wrong in step Looking for vboxmanage.exe

I just installed Docker Toolbox on my windows 7 machine. After installing I run the Docker Quickstart terminal which displays the following message:

Looks something went wrong in step nLooking for vboxmanage.exen... Press any key to continue....

Anyone here who knows how to solve this?

Regards,

The same thing happened to me. At this moment I am using Windows Home.

At least in my case, what happened was that the environment variables DOCKER_MACHINE and DOCKER_TOOLBOX_INSTALL_PATH were not created for the system.

I just had to add them and it worked.

Docker, looks like something went wrong in step ́looking for vboxmanage.exe press any key to Duration: 2:44 Posted: Oct 21, 2019 I provided the bash.exe path from git folder and upon again double clicking the “Docker Quickstart Terminal” icon: it opens command prompt and gives the error: “Looks like something went wrong in step ´Looking for vboxmanage.exe´… Press any key to continue…” Any help on this, thanks. Regards.

Solved the problem by cleaning my .bashrc file. More specific, i removed the cd , which makes perfectly sense.

Docker quick start treminal fails to start on Windows 10 with , More details may be available in 'C:\Users\napas\. docker\machine\machines\default\default\Logs\VBoxHardening. log VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine Looks like something went wrong in step ´Checking status on default´ Press any key to continue If you get this message: Looks like something went wrong in step ´Looking for vboxmanage.exe´ Press any key to continue" when you click on "Docker Quickstart Terminal", try the following.

For me, the problem was that the DOCKER_TOOLBOX_INSTALLPATH was only set for the user used to escalate priviligies at installation. When I run Docker Quickstart as my regular user, the DOCKER_TOOLBOX_INSTALLPATH variable is empty, producing the error. Setting DOCKER_TOOLBOX_INSTALLPATH system wide solved the problem.

Docker settings for native windows 7 enterprise, If you see this message: looks like something went wrong in step 'looking for vboxmanage.exe'. Make sure these environment variables are set:. looks like something went wrong in step ́looking for vboxmanage.exe press any key to continue

I'm Windows 8.1 user, I got the same problem when I installing the Docker Toolbox.

Because I have a previous version of VirtualBox installed, so I uncheck the VirtualBox install option in the Docker Toolbox installer.

After the install and I run Docker Quickstart terminal and get the same problem looks like something went wrong in step 'looking for vboxmanage.exe'.

Look at the file D:\Docker Toolbox\start.sh, there are some code fragment:

STEP="Looking for vboxmanage.exe"
if [ ! -z "$VBOX_MSI_INSTALL_PATH" ]; then
  VBOXMANAGE="${VBOX_MSI_INSTALL_PATH}VBoxManage.exe"
else
  VBOXMANAGE="${VBOX_INSTALL_PATH}VBoxManage.exe"
fi

The start.sh use $VBOX_MSI_INSTALL_PATH and ${VBOX_INSTALL_PATH} Environment Variables to locate the VBoxManage.exe.

And I find my system variables VBOX_MSI_INSTALL_PATH is

D:\VirtualBox

and then, I change it to

D:\VirtualBox\

It works fine!

Or maybe you miss the VBOX_MSI_INSTALL_PATH/VBOX_INSTALL_PATH Environment Variables.

This is my first answer on stackoverflow, I hope this will help you! Finally forgive my poor english ):

Looks like something went wrong in step - Docker Toolbox, VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine. Looks like something went wrong  After the install and I run Docker Quickstart terminal and get the same problem looks like something went wrong in step 'looking for vboxmanage.exe'. Look at the file D:\Docker Toolbox\start.sh , there are some code fragment:

For me, it helped to start Docker Quickstart Terminal with admin privileges.

#1 – 'Looking for vboxmanage.exe' – Docker Toolbox error, The solution was uninstall VirtualBox, eliminate all configuration directory (both VirtualBox and Docker one). Here the steps: Go to Control Panel,  Looks like somethings went wrong is step looking for vboxmanage.exe Mismo caso ocurre al ejecutar Kitematic Con estos pasos se soluciona el problema rapido y facil. Siganos en mi twitter

Installing docker Toolbox under windows failed to start Docker , Windows7(64) failed to start Docker Quickstart Terminal after /bin/bash trap '[ "​$?" -eq 0 ] || read -p "Looks like something went wrong in step ´$STEP´ Press docker-machine.exe STEP="Looking for vboxmanage.exe" if [ ! More details may be av ailable in 'C:\Users\NguyenThanh\.docker\machine\machines\default\default\Logs\V BoxHardening.log' VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine Looks like something went wrong in step 'Checking if machine default exists' Press any key to continue

Docker: Looks something went wrong in step Looking for , After the install and I run Docker Quickstart terminal and get the same problem looks like something went wrong in step 'looking for vboxmanage.exe'. Look at  After restarting machine and opening the Docker Quickstart Terminal, I get the following error: Unable to start the VM: C:\\Program Files\\Oracle\\VirtualBox\\VBoxManage.exe startvm default --type

netcat not able to run in windows 10 - netcat,

Comments
  • docker_machine shouldn't be needed, it is derived from D_T_I_P
  • yes, it's worked for me because i had already installed virtualbox.
  • For me, on Windows 10 Home, even after adding the environment variables, it didn't work. After running Docker Quickstart Terminal as an administrator, it worked right away.
  • To be more specific, if you used git bash in the past and have set a default path (so git opens in your project path each time) you like have a .bashrc file with a line like this cd ../../PATH/TO/MY-DIR/ This line is what is causing the problem for Docker quick start. Just open the file and delete the line and run the docker quick start again.
  • Hi, I have the same problem, where is this file? @GlenF.
  • Mine was in the root user directory.
  • I had the same issue. Good catch!
  • Awesome catch indeed. Thank you!
  • Admin user or put the variable under System variable would do the work.
  • ^ This. A neat solution and doesn't involve mucking with your .bashrc.
  • Great works nicely, and also note bash start.sh doesn't show the line outputs.
  • Thanks, also did the investigation myself, but took me an hour to find this.