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,
docker virtualbox
add a comment |
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,
docker virtualbox
add a comment |
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,
docker virtualbox
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,
docker virtualbox
docker virtualbox
asked Sep 7 '16 at 14:54
Bgvv1983
7341522
7341522
add a comment |
add a comment |
13 Answers
13
active
oldest
votes
Solved the problem by cleaning my .bashrc file.
More specific, i removed the cd , which makes perfectly sense.
1
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.
– Glen F.
Sep 3 '17 at 5:05
add a comment |
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 Toolboxstart.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 ):
add a comment |
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.
I had the same issue. Good catch!
– Ron
Apr 23 at 14:47
Awesome catch indeed. Thank you!
– Valery
Oct 24 at 15:20
add a comment |
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_machine shouldn't be needed, it is derived from D_T_I_P
– Barett
Sep 14 at 21:26
add a comment |
For me, it helped to start Docker Quickstart Terminal with admin privileges.
add a comment |
This works if you do not have admin rights:
> Setx DOCKER_MACHINE "C:Program FilesDocker Toolboxdocker-machine.exe"
> Setx DOCKER_TOOLBOX_INSTALL_PATH "C:Program FilesDocker Toolbox\"
> Setx VBOX_MSI_INSTALL_PATH "C:Program FilesOracleVirtualBox\"
The double backslash in the end makes sure that the variable is saved with one backslash as last character, needed in C:Program FilesDocker Toolboxstart.sh
:
> echo %DOCKER_TOOLBOX_INSTALL_PATH%
C:Program FilesDocker Toolbox
add a comment |
Due to the relative DOCKER_MACHINE
path definition on L10, it seems that start.sh
will only run when you are inside its directory. I fixed it by modifying the target of the "Docker Quickstart Terminal" shortcut as follows:
C:ToolsGitgit-bash.exe -c "cd /c/tools/docker; ./start.sh"
Substitute the paths to GitBash and Docker Toolbox to match your installations. If your paths contain spaces, be sure to wrap them in quotes as usual. For example:
"C:ToolsGit Bashgit-bash.exe" -c "cd '/c/tools/docker toolbox'; ./start.sh"
For context, I had GitBash and VirtualBox already installed before installing Docker Toolbox, so I deselected those options during its install. I'm sure that if I went with the default options, this issue wouldn't have happened. That's probably why some folks on GitHub suggest uninstalling VirtualBox and re-installing Docker Toolbox. Don't do that, it's almost certainly unnecessary.
^ This. A neat solution and doesn't involve mucking with your.bashrc
.
– Omni
Mar 20 at 9:21
add a comment |
Simple solution: I thought I could just double click on it, but instead need to bring up a windows command prompt, CD to C:Program FilesDocker Toolbox , and type
sh start.sh
Great works nicely, and also notebash start.sh
doesn't show the line outputs.
– Ricky Boyce
Nov 7 '17 at 10:13
add a comment |
Running docker as Administrator solved the problem for me.
add a comment |
I personally solved this issue by adding the following property to my env (Windows Env variables):
DOCKER_TOOLBOX_INSTALL_PATH=C:Program FilesDocker Toolbox
as pointed out by the start.sh
script of the Docker Toolbox installation.
add a comment |
Do you know how good an open-source program is?
You can actually investigate the issue yourselve, which could be way more precise.
please scroll the quickstart terminal up and see which error message you have got
open C:Program FilesDocker Toolboxstart.sh (Where you install docker toolbox) with text editer, e.g. sublime text
and see the codesif it is in step "looking for vboxmange.exe", it should be before STEP="Checking if machine $VM exists" and there are only 50 lines to read
As of 2018-11-27, the only two error that could be given in this step is from these lines, so investigate and find your error in it:
which are:
if [ ! -f "${DOCKER_MACHINE}" ]; then
echo "Docker Machine is not installed. Please re-run the Toolbox Installer and try again."
exit 1
fi
if [ ! -f "${VBOXMANAGE}" ]; then
echo "VirtualBox is not installed. Please re-run the Toolbox Installer and try again."
exit 1
fi
In which:
DOCKER_MACHINE="${DOCKER_TOOLBOX_INSTALL_PATH}docker-machine.exe"
And
if [ ! -z "$VBOX_MSI_INSTALL_PATH" ]; then
VBOXMANAGE="${VBOX_MSI_INSTALL_PATH}VBoxManage.exe"
else
VBOXMANAGE="${VBOX_INSTALL_PATH}VBoxManage.exe"
fi
So, check your environmental variables and echo it.
In my case, the reason is that DOCKER_TOOLBOX_INSTALL_PATH is an admin user variable:
So, run the quickstart terminal as admin user or put the variable under System variable would do the work
add a comment |
You can solve this reinstalling the VirtualBox, choosing repair mode.
C:Program FilesDocker Toolboxinstallersvirtualbox -> virtualbox.exe
enter image description here
After finished the process, restart you machine and smile!
add a comment |
Docker Tool Box is not a standalone application. It has many other tools like Oracle Virtual Box, Git & docker engine itself.
./start.sh
is seeking some existing configuration which might miss in the older version. I updated the GIT version from 2.0.x
to 2.12.x
& it works for me.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f39373217%2fdocker-looks-something-went-wrong-in-step-looking-for-vboxmanage-exe%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
13 Answers
13
active
oldest
votes
13 Answers
13
active
oldest
votes
active
oldest
votes
active
oldest
votes
Solved the problem by cleaning my .bashrc file.
More specific, i removed the cd , which makes perfectly sense.
1
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.
– Glen F.
Sep 3 '17 at 5:05
add a comment |
Solved the problem by cleaning my .bashrc file.
More specific, i removed the cd , which makes perfectly sense.
1
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.
– Glen F.
Sep 3 '17 at 5:05
add a comment |
Solved the problem by cleaning my .bashrc file.
More specific, i removed the cd , which makes perfectly sense.
Solved the problem by cleaning my .bashrc file.
More specific, i removed the cd , which makes perfectly sense.
edited Sep 8 '16 at 10:40
answered Sep 7 '16 at 21:17
Bgvv1983
7341522
7341522
1
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.
– Glen F.
Sep 3 '17 at 5:05
add a comment |
1
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.
– Glen F.
Sep 3 '17 at 5:05
1
1
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.
– Glen F.
Sep 3 '17 at 5:05
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.
– Glen F.
Sep 3 '17 at 5:05
add a comment |
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 Toolboxstart.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 ):
add a comment |
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 Toolboxstart.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 ):
add a comment |
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 Toolboxstart.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 ):
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 Toolboxstart.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 ):
edited Mar 1 at 14:26
answered Mar 11 '17 at 10:16
kinginblue
8123
8123
add a comment |
add a comment |
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.
I had the same issue. Good catch!
– Ron
Apr 23 at 14:47
Awesome catch indeed. Thank you!
– Valery
Oct 24 at 15:20
add a comment |
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.
I had the same issue. Good catch!
– Ron
Apr 23 at 14:47
Awesome catch indeed. Thank you!
– Valery
Oct 24 at 15:20
add a comment |
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.
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.
edited Mar 28 at 11:01
Harun Diluka Heshan
7692721
7692721
answered Mar 28 at 7:00
Mats Nordqvist
8112
8112
I had the same issue. Good catch!
– Ron
Apr 23 at 14:47
Awesome catch indeed. Thank you!
– Valery
Oct 24 at 15:20
add a comment |
I had the same issue. Good catch!
– Ron
Apr 23 at 14:47
Awesome catch indeed. Thank you!
– Valery
Oct 24 at 15:20
I had the same issue. Good catch!
– Ron
Apr 23 at 14:47
I had the same issue. Good catch!
– Ron
Apr 23 at 14:47
Awesome catch indeed. Thank you!
– Valery
Oct 24 at 15:20
Awesome catch indeed. Thank you!
– Valery
Oct 24 at 15:20
add a comment |
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_machine shouldn't be needed, it is derived from D_T_I_P
– Barett
Sep 14 at 21:26
add a comment |
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_machine shouldn't be needed, it is derived from D_T_I_P
– Barett
Sep 14 at 21:26
add a comment |
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.
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.
edited May 15 at 12:59
anothernode
2,681102541
2,681102541
answered May 15 at 12:33
kiviev
7111
7111
docker_machine shouldn't be needed, it is derived from D_T_I_P
– Barett
Sep 14 at 21:26
add a comment |
docker_machine shouldn't be needed, it is derived from D_T_I_P
– Barett
Sep 14 at 21:26
docker_machine shouldn't be needed, it is derived from D_T_I_P
– Barett
Sep 14 at 21:26
docker_machine shouldn't be needed, it is derived from D_T_I_P
– Barett
Sep 14 at 21:26
add a comment |
For me, it helped to start Docker Quickstart Terminal with admin privileges.
add a comment |
For me, it helped to start Docker Quickstart Terminal with admin privileges.
add a comment |
For me, it helped to start Docker Quickstart Terminal with admin privileges.
For me, it helped to start Docker Quickstart Terminal with admin privileges.
answered Jul 27 at 19:43
Artur Łysik
15124
15124
add a comment |
add a comment |
This works if you do not have admin rights:
> Setx DOCKER_MACHINE "C:Program FilesDocker Toolboxdocker-machine.exe"
> Setx DOCKER_TOOLBOX_INSTALL_PATH "C:Program FilesDocker Toolbox\"
> Setx VBOX_MSI_INSTALL_PATH "C:Program FilesOracleVirtualBox\"
The double backslash in the end makes sure that the variable is saved with one backslash as last character, needed in C:Program FilesDocker Toolboxstart.sh
:
> echo %DOCKER_TOOLBOX_INSTALL_PATH%
C:Program FilesDocker Toolbox
add a comment |
This works if you do not have admin rights:
> Setx DOCKER_MACHINE "C:Program FilesDocker Toolboxdocker-machine.exe"
> Setx DOCKER_TOOLBOX_INSTALL_PATH "C:Program FilesDocker Toolbox\"
> Setx VBOX_MSI_INSTALL_PATH "C:Program FilesOracleVirtualBox\"
The double backslash in the end makes sure that the variable is saved with one backslash as last character, needed in C:Program FilesDocker Toolboxstart.sh
:
> echo %DOCKER_TOOLBOX_INSTALL_PATH%
C:Program FilesDocker Toolbox
add a comment |
This works if you do not have admin rights:
> Setx DOCKER_MACHINE "C:Program FilesDocker Toolboxdocker-machine.exe"
> Setx DOCKER_TOOLBOX_INSTALL_PATH "C:Program FilesDocker Toolbox\"
> Setx VBOX_MSI_INSTALL_PATH "C:Program FilesOracleVirtualBox\"
The double backslash in the end makes sure that the variable is saved with one backslash as last character, needed in C:Program FilesDocker Toolboxstart.sh
:
> echo %DOCKER_TOOLBOX_INSTALL_PATH%
C:Program FilesDocker Toolbox
This works if you do not have admin rights:
> Setx DOCKER_MACHINE "C:Program FilesDocker Toolboxdocker-machine.exe"
> Setx DOCKER_TOOLBOX_INSTALL_PATH "C:Program FilesDocker Toolbox\"
> Setx VBOX_MSI_INSTALL_PATH "C:Program FilesOracleVirtualBox\"
The double backslash in the end makes sure that the variable is saved with one backslash as last character, needed in C:Program FilesDocker Toolboxstart.sh
:
> echo %DOCKER_TOOLBOX_INSTALL_PATH%
C:Program FilesDocker Toolbox
answered Oct 12 at 8:28
janobeber
311
311
add a comment |
add a comment |
Due to the relative DOCKER_MACHINE
path definition on L10, it seems that start.sh
will only run when you are inside its directory. I fixed it by modifying the target of the "Docker Quickstart Terminal" shortcut as follows:
C:ToolsGitgit-bash.exe -c "cd /c/tools/docker; ./start.sh"
Substitute the paths to GitBash and Docker Toolbox to match your installations. If your paths contain spaces, be sure to wrap them in quotes as usual. For example:
"C:ToolsGit Bashgit-bash.exe" -c "cd '/c/tools/docker toolbox'; ./start.sh"
For context, I had GitBash and VirtualBox already installed before installing Docker Toolbox, so I deselected those options during its install. I'm sure that if I went with the default options, this issue wouldn't have happened. That's probably why some folks on GitHub suggest uninstalling VirtualBox and re-installing Docker Toolbox. Don't do that, it's almost certainly unnecessary.
^ This. A neat solution and doesn't involve mucking with your.bashrc
.
– Omni
Mar 20 at 9:21
add a comment |
Due to the relative DOCKER_MACHINE
path definition on L10, it seems that start.sh
will only run when you are inside its directory. I fixed it by modifying the target of the "Docker Quickstart Terminal" shortcut as follows:
C:ToolsGitgit-bash.exe -c "cd /c/tools/docker; ./start.sh"
Substitute the paths to GitBash and Docker Toolbox to match your installations. If your paths contain spaces, be sure to wrap them in quotes as usual. For example:
"C:ToolsGit Bashgit-bash.exe" -c "cd '/c/tools/docker toolbox'; ./start.sh"
For context, I had GitBash and VirtualBox already installed before installing Docker Toolbox, so I deselected those options during its install. I'm sure that if I went with the default options, this issue wouldn't have happened. That's probably why some folks on GitHub suggest uninstalling VirtualBox and re-installing Docker Toolbox. Don't do that, it's almost certainly unnecessary.
^ This. A neat solution and doesn't involve mucking with your.bashrc
.
– Omni
Mar 20 at 9:21
add a comment |
Due to the relative DOCKER_MACHINE
path definition on L10, it seems that start.sh
will only run when you are inside its directory. I fixed it by modifying the target of the "Docker Quickstart Terminal" shortcut as follows:
C:ToolsGitgit-bash.exe -c "cd /c/tools/docker; ./start.sh"
Substitute the paths to GitBash and Docker Toolbox to match your installations. If your paths contain spaces, be sure to wrap them in quotes as usual. For example:
"C:ToolsGit Bashgit-bash.exe" -c "cd '/c/tools/docker toolbox'; ./start.sh"
For context, I had GitBash and VirtualBox already installed before installing Docker Toolbox, so I deselected those options during its install. I'm sure that if I went with the default options, this issue wouldn't have happened. That's probably why some folks on GitHub suggest uninstalling VirtualBox and re-installing Docker Toolbox. Don't do that, it's almost certainly unnecessary.
Due to the relative DOCKER_MACHINE
path definition on L10, it seems that start.sh
will only run when you are inside its directory. I fixed it by modifying the target of the "Docker Quickstart Terminal" shortcut as follows:
C:ToolsGitgit-bash.exe -c "cd /c/tools/docker; ./start.sh"
Substitute the paths to GitBash and Docker Toolbox to match your installations. If your paths contain spaces, be sure to wrap them in quotes as usual. For example:
"C:ToolsGit Bashgit-bash.exe" -c "cd '/c/tools/docker toolbox'; ./start.sh"
For context, I had GitBash and VirtualBox already installed before installing Docker Toolbox, so I deselected those options during its install. I'm sure that if I went with the default options, this issue wouldn't have happened. That's probably why some folks on GitHub suggest uninstalling VirtualBox and re-installing Docker Toolbox. Don't do that, it's almost certainly unnecessary.
answered Sep 4 '17 at 2:03
Illya Moskvin
219313
219313
^ This. A neat solution and doesn't involve mucking with your.bashrc
.
– Omni
Mar 20 at 9:21
add a comment |
^ This. A neat solution and doesn't involve mucking with your.bashrc
.
– Omni
Mar 20 at 9:21
^ This. A neat solution and doesn't involve mucking with your
.bashrc
.– Omni
Mar 20 at 9:21
^ This. A neat solution and doesn't involve mucking with your
.bashrc
.– Omni
Mar 20 at 9:21
add a comment |
Simple solution: I thought I could just double click on it, but instead need to bring up a windows command prompt, CD to C:Program FilesDocker Toolbox , and type
sh start.sh
Great works nicely, and also notebash start.sh
doesn't show the line outputs.
– Ricky Boyce
Nov 7 '17 at 10:13
add a comment |
Simple solution: I thought I could just double click on it, but instead need to bring up a windows command prompt, CD to C:Program FilesDocker Toolbox , and type
sh start.sh
Great works nicely, and also notebash start.sh
doesn't show the line outputs.
– Ricky Boyce
Nov 7 '17 at 10:13
add a comment |
Simple solution: I thought I could just double click on it, but instead need to bring up a windows command prompt, CD to C:Program FilesDocker Toolbox , and type
sh start.sh
Simple solution: I thought I could just double click on it, but instead need to bring up a windows command prompt, CD to C:Program FilesDocker Toolbox , and type
sh start.sh
answered Jul 21 '17 at 17:58
rhinmass
11015
11015
Great works nicely, and also notebash start.sh
doesn't show the line outputs.
– Ricky Boyce
Nov 7 '17 at 10:13
add a comment |
Great works nicely, and also notebash start.sh
doesn't show the line outputs.
– Ricky Boyce
Nov 7 '17 at 10:13
Great works nicely, and also note
bash start.sh
doesn't show the line outputs.– Ricky Boyce
Nov 7 '17 at 10:13
Great works nicely, and also note
bash start.sh
doesn't show the line outputs.– Ricky Boyce
Nov 7 '17 at 10:13
add a comment |
Running docker as Administrator solved the problem for me.
add a comment |
Running docker as Administrator solved the problem for me.
add a comment |
Running docker as Administrator solved the problem for me.
Running docker as Administrator solved the problem for me.
answered Nov 1 at 16:22
Jonathan Ramos
536614
536614
add a comment |
add a comment |
I personally solved this issue by adding the following property to my env (Windows Env variables):
DOCKER_TOOLBOX_INSTALL_PATH=C:Program FilesDocker Toolbox
as pointed out by the start.sh
script of the Docker Toolbox installation.
add a comment |
I personally solved this issue by adding the following property to my env (Windows Env variables):
DOCKER_TOOLBOX_INSTALL_PATH=C:Program FilesDocker Toolbox
as pointed out by the start.sh
script of the Docker Toolbox installation.
add a comment |
I personally solved this issue by adding the following property to my env (Windows Env variables):
DOCKER_TOOLBOX_INSTALL_PATH=C:Program FilesDocker Toolbox
as pointed out by the start.sh
script of the Docker Toolbox installation.
I personally solved this issue by adding the following property to my env (Windows Env variables):
DOCKER_TOOLBOX_INSTALL_PATH=C:Program FilesDocker Toolbox
as pointed out by the start.sh
script of the Docker Toolbox installation.
answered Nov 12 at 16:44
Mahieddine M. Ichir
14525
14525
add a comment |
add a comment |
Do you know how good an open-source program is?
You can actually investigate the issue yourselve, which could be way more precise.
please scroll the quickstart terminal up and see which error message you have got
open C:Program FilesDocker Toolboxstart.sh (Where you install docker toolbox) with text editer, e.g. sublime text
and see the codesif it is in step "looking for vboxmange.exe", it should be before STEP="Checking if machine $VM exists" and there are only 50 lines to read
As of 2018-11-27, the only two error that could be given in this step is from these lines, so investigate and find your error in it:
which are:
if [ ! -f "${DOCKER_MACHINE}" ]; then
echo "Docker Machine is not installed. Please re-run the Toolbox Installer and try again."
exit 1
fi
if [ ! -f "${VBOXMANAGE}" ]; then
echo "VirtualBox is not installed. Please re-run the Toolbox Installer and try again."
exit 1
fi
In which:
DOCKER_MACHINE="${DOCKER_TOOLBOX_INSTALL_PATH}docker-machine.exe"
And
if [ ! -z "$VBOX_MSI_INSTALL_PATH" ]; then
VBOXMANAGE="${VBOX_MSI_INSTALL_PATH}VBoxManage.exe"
else
VBOXMANAGE="${VBOX_INSTALL_PATH}VBoxManage.exe"
fi
So, check your environmental variables and echo it.
In my case, the reason is that DOCKER_TOOLBOX_INSTALL_PATH is an admin user variable:
So, run the quickstart terminal as admin user or put the variable under System variable would do the work
add a comment |
Do you know how good an open-source program is?
You can actually investigate the issue yourselve, which could be way more precise.
please scroll the quickstart terminal up and see which error message you have got
open C:Program FilesDocker Toolboxstart.sh (Where you install docker toolbox) with text editer, e.g. sublime text
and see the codesif it is in step "looking for vboxmange.exe", it should be before STEP="Checking if machine $VM exists" and there are only 50 lines to read
As of 2018-11-27, the only two error that could be given in this step is from these lines, so investigate and find your error in it:
which are:
if [ ! -f "${DOCKER_MACHINE}" ]; then
echo "Docker Machine is not installed. Please re-run the Toolbox Installer and try again."
exit 1
fi
if [ ! -f "${VBOXMANAGE}" ]; then
echo "VirtualBox is not installed. Please re-run the Toolbox Installer and try again."
exit 1
fi
In which:
DOCKER_MACHINE="${DOCKER_TOOLBOX_INSTALL_PATH}docker-machine.exe"
And
if [ ! -z "$VBOX_MSI_INSTALL_PATH" ]; then
VBOXMANAGE="${VBOX_MSI_INSTALL_PATH}VBoxManage.exe"
else
VBOXMANAGE="${VBOX_INSTALL_PATH}VBoxManage.exe"
fi
So, check your environmental variables and echo it.
In my case, the reason is that DOCKER_TOOLBOX_INSTALL_PATH is an admin user variable:
So, run the quickstart terminal as admin user or put the variable under System variable would do the work
add a comment |
Do you know how good an open-source program is?
You can actually investigate the issue yourselve, which could be way more precise.
please scroll the quickstart terminal up and see which error message you have got
open C:Program FilesDocker Toolboxstart.sh (Where you install docker toolbox) with text editer, e.g. sublime text
and see the codesif it is in step "looking for vboxmange.exe", it should be before STEP="Checking if machine $VM exists" and there are only 50 lines to read
As of 2018-11-27, the only two error that could be given in this step is from these lines, so investigate and find your error in it:
which are:
if [ ! -f "${DOCKER_MACHINE}" ]; then
echo "Docker Machine is not installed. Please re-run the Toolbox Installer and try again."
exit 1
fi
if [ ! -f "${VBOXMANAGE}" ]; then
echo "VirtualBox is not installed. Please re-run the Toolbox Installer and try again."
exit 1
fi
In which:
DOCKER_MACHINE="${DOCKER_TOOLBOX_INSTALL_PATH}docker-machine.exe"
And
if [ ! -z "$VBOX_MSI_INSTALL_PATH" ]; then
VBOXMANAGE="${VBOX_MSI_INSTALL_PATH}VBoxManage.exe"
else
VBOXMANAGE="${VBOX_INSTALL_PATH}VBoxManage.exe"
fi
So, check your environmental variables and echo it.
In my case, the reason is that DOCKER_TOOLBOX_INSTALL_PATH is an admin user variable:
So, run the quickstart terminal as admin user or put the variable under System variable would do the work
Do you know how good an open-source program is?
You can actually investigate the issue yourselve, which could be way more precise.
please scroll the quickstart terminal up and see which error message you have got
open C:Program FilesDocker Toolboxstart.sh (Where you install docker toolbox) with text editer, e.g. sublime text
and see the codesif it is in step "looking for vboxmange.exe", it should be before STEP="Checking if machine $VM exists" and there are only 50 lines to read
As of 2018-11-27, the only two error that could be given in this step is from these lines, so investigate and find your error in it:
which are:
if [ ! -f "${DOCKER_MACHINE}" ]; then
echo "Docker Machine is not installed. Please re-run the Toolbox Installer and try again."
exit 1
fi
if [ ! -f "${VBOXMANAGE}" ]; then
echo "VirtualBox is not installed. Please re-run the Toolbox Installer and try again."
exit 1
fi
In which:
DOCKER_MACHINE="${DOCKER_TOOLBOX_INSTALL_PATH}docker-machine.exe"
And
if [ ! -z "$VBOX_MSI_INSTALL_PATH" ]; then
VBOXMANAGE="${VBOX_MSI_INSTALL_PATH}VBoxManage.exe"
else
VBOXMANAGE="${VBOX_INSTALL_PATH}VBoxManage.exe"
fi
So, check your environmental variables and echo it.
In my case, the reason is that DOCKER_TOOLBOX_INSTALL_PATH is an admin user variable:
So, run the quickstart terminal as admin user or put the variable under System variable would do the work
edited Nov 27 at 10:22
answered Nov 27 at 10:17
Near
337
337
add a comment |
add a comment |
You can solve this reinstalling the VirtualBox, choosing repair mode.
C:Program FilesDocker Toolboxinstallersvirtualbox -> virtualbox.exe
enter image description here
After finished the process, restart you machine and smile!
add a comment |
You can solve this reinstalling the VirtualBox, choosing repair mode.
C:Program FilesDocker Toolboxinstallersvirtualbox -> virtualbox.exe
enter image description here
After finished the process, restart you machine and smile!
add a comment |
You can solve this reinstalling the VirtualBox, choosing repair mode.
C:Program FilesDocker Toolboxinstallersvirtualbox -> virtualbox.exe
enter image description here
After finished the process, restart you machine and smile!
You can solve this reinstalling the VirtualBox, choosing repair mode.
C:Program FilesDocker Toolboxinstallersvirtualbox -> virtualbox.exe
enter image description here
After finished the process, restart you machine and smile!
answered Dec 6 at 10:38
Renan Shin Iti
1
1
add a comment |
add a comment |
Docker Tool Box is not a standalone application. It has many other tools like Oracle Virtual Box, Git & docker engine itself.
./start.sh
is seeking some existing configuration which might miss in the older version. I updated the GIT version from 2.0.x
to 2.12.x
& it works for me.
add a comment |
Docker Tool Box is not a standalone application. It has many other tools like Oracle Virtual Box, Git & docker engine itself.
./start.sh
is seeking some existing configuration which might miss in the older version. I updated the GIT version from 2.0.x
to 2.12.x
& it works for me.
add a comment |
Docker Tool Box is not a standalone application. It has many other tools like Oracle Virtual Box, Git & docker engine itself.
./start.sh
is seeking some existing configuration which might miss in the older version. I updated the GIT version from 2.0.x
to 2.12.x
& it works for me.
Docker Tool Box is not a standalone application. It has many other tools like Oracle Virtual Box, Git & docker engine itself.
./start.sh
is seeking some existing configuration which might miss in the older version. I updated the GIT version from 2.0.x
to 2.12.x
& it works for me.
edited Jun 23 '17 at 5:35
The Dictator
2,72042741
2,72042741
answered Jun 20 '17 at 9:39
user196470
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f39373217%2fdocker-looks-something-went-wrong-in-step-looking-for-vboxmanage-exe%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown