9
2
I'm on Windows 7, VirtualBox 5.0.4, Docker toolbox 1.9.0. When I run the quickstart I get:
Creating Machine default...
Running pre-create checks...
Creating machine...
Error creating machine: Error in driver during machine creation: Maximum number of retries (5) exceeded
Looks like something went wrong... Press any key to continue...
But I do get a running 'default' VM when I open VirtualBox and have a look. In my VBox.log I see (full file is here):
00:00:00.696246 HM: HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support
So maybe VT-X support is ok for me. Right at the end of the logfile I see somthing ominous about D-Bus not being installed:
00:00:46.950561 VMMDev: Guest Log: 00:00:10.018836 vminfo Error: Unable to connect to system D-Bus (3/3): D-Bus not installed
The D-Bus issue has been reported here https://github.com/docker/toolbox/issues/214 When I run the quickstart again directly after this, I get an error message about getting an IP address:
Machine default already exists in VirtualBox.
Setting environment variables for machine default...
Error running connection boilerplate: Error getting driver URL: Something went wrong running an SSH command!
command : ip addr show dev eth1
err : exit status 255
output :
## .
## ## ## ==
## ## ## ## ## ===
/"""""""""""""""""\___/ ===
~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ / ===- ~~~
\______ o __/
\ \ __/
\____\_______/
Error getting IP address: Something went wrong running an SSH command!
command : ip addr show dev eth1
err : exit status 255
output :
docker is configured to use the default machine with IP
For help getting started, check out the docs at https://docs.docker.com
NOTE: When using interactive commands, prepend winpty. Examples: 'winpty docker run -it ...', 'winpty docker exec -it ...'.
And if I run a command, I get another message relating to connecting:
$ winpty docker run hello-world
An error occurred trying to connect: Post http://localhost:2375/v1.21/containers
/create: dial tcp 127.0.0.1:2375: ConnectEx tcp: No connection could be made because the target machine actively refused it.
At this point I went to https://www.virtualbox.org/wiki/Testbuilds and got VirtualBox 5.0.9, and then uninstalled Docker Toolboox, deleted the default VM and the .docker directory, and reinstalled the Toolbox, and re-run it, and got the same problem:
Creating Machine default...
Creating CA: C:\Users\marwick\.docker\machine\certs\ca.pem
Creating client certificate: C:\Users\marwick\.docker\machine\certs\cert.pem
Running pre-create checks...
Creating machine...
Error creating machine: Error in driver during machine creation: Maximum number of retries (5) exceeded
Looks like something went wrong... Press any key to continue...
The logfile for this attempt is here: http://pastebin.com/9VjD9t6P
How can I get this working?
This solution worked for me as well. – Oliver Burdekin – 2015-11-10T19:17:08.743
I'm glad it's working for others, but I've done this several times, and deleting the dotfiles associated with the VM, and there's no improvement. – Ben – 2015-11-11T00:10:41.017
@Ben you ought to delete files from within virtualbox UI (delete all files) – MediaVince – 2016-12-06T14:06:29.483