docker-archive / toolbox

The Docker Toolbox
https://docker.com/toolbox
3.21k stars 1.23k forks source link

Issue running Windows's Docker Quickstart Terminal. #496

Open sparksThefire opened 8 years ago

sparksThefire commented 8 years ago

After a fresh install of the Docker Toolbox (v1.11.1b), the Quickstart terminal cannot find vboxmanager.exe with the error message of Docker Machine is not installed. Please re-run the Toolbox Installer and try again. when a .bash_profile or .bash_rc changes the path.

I identified the issue and corrected it on my end but am writing an error in case anyone else has this issue and maybe there will be a fix in the installation.

Here is the setup: I am running Windows 7, but regularly go into my git shell dealing with work projects. Because of this, I have a .bash_profile that contains a cd into my github directory (~/Documents/Github). When I start the Docker Quickstart Terminal, despite the shortcut supposedly opening in the docker install directory (C:\Program Files\Docker Toolbox), it opens into my github directory. This means it can't find the ./docker-machine.exe file since it is looking for ~\Documents\Github\docker-machine.exe and not /c/Program\ Files/Docker\ Toolbox/docker-machine.exe

My local fix is to edit start.sh and insert cd /c/Program\ Files/Docker\ Toolbox/ on line 5. Normally running Docker Quickstart Terminal now works.

Additionally, after adding this line, it still opens into my ~/Documents/Github so it seems that it is pulling data on terminal launch and again after docker boots up the vm.

ljack commented 8 years ago

+1

warong commented 7 years ago

Thanks! This fixed my problem as well since I too have a .profile that changes to my work directory when running Git bash.

Docker Toolbox's start.sh should account for this user scenario.

jcollum-cambia commented 7 years ago

Wow a year later this hasn't been addressed?

EMCP commented 6 years ago

my git bash starts in a network drive for some odd reason, also causing issues with docker-toolbox

saira05 commented 6 years ago

i used this line edited in start.sh but issue is not resolved for me. why?

Sipsip commented 6 years ago

adding

cd /c/Program\ Files/Docker\ Toolbox/

in start.sh doesn't fix the issue for me unfortunately

sparksThefire commented 6 years ago

/c/Program\ Files/Docker\ Toolbox/ is the default location of the Docker Toolbox. Please check to see if your toolbox is installed in the same directory. If it's installed in a different location, change the cd command to your toolbox location.

usoliveira commented 6 years ago

In my case, the problem was because the DOCKER system variables was setted only for the "admin" user. Because I was trying to run as a normal user, it doesn't find those variables and even the docker tools install dir. I moved those variables to my current user system variable settings, and everything is OK now!

fousu commented 5 years ago

@usoliveira , Thanks!.

getsmarter01 commented 5 years ago

I Just installed Docker Toolbox on my windows 8 my virtual machine is already Enabled

also this info may help: Microsoft Windows [Version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Abu_Moh>docker-machine ls NAME ACTIVE DRIVER STATE URL SWARM DO CKER ERRORS default - virtualbox Running tcp://192.168.99.100:2376 v1 8.09.3

C:\Users\Abu_Moh>

I tries to run (Docker Quickstart Terminal) and it gives me this error: "Looks like something went wrong in step 'Setting env'...Press any key to continue..."

please help.... I just started Jupyter notebook course, and stuck in this setup thanx

========

bryan-lima commented 4 years ago

In my case, the problem was because the DOCKER system variables was setted only for the "admin" user. Because I was trying to run as a normal user, it doesn't find those variables and even the docker tools install dir. I moved those variables to my current user system variable settings, and everything is OK now!

@usoliveira, could you report here the changes you made?

usoliveira commented 4 years ago

@bryan-lima I don't have it written anymore, but if you look at your system environment variables (using an administrator account in Windows), it will show you all docker variables that Docker for Windows created. Just copy all of them, and create it in your current Windows user env variables. Now it should works properly!