Closed suriyaa closed 8 years ago
C:\Users\Suriyaa\Downloads\docker>docker-machine create --driver hyperv vm
Running pre-create checks...
Error with pre-create check: "read tcp 127.0.0.1:7809->127.0.0.1:7808: wsarecv: Eine vorhandene Verbindung wurde vom Remotehost geschlossen."
Error attempting heartbeat call to plugin server: connection is shut down
C:\Users\Suriyaa\Downloads\docker>docker-machine restart default
Restarting "default"...
Waiting for SSH to be available...
Detecting the provisioner...
OS type not recognized
C:\Users\Suriyaa\Downloads\docker>
I think I solved it with these commands!
Use another name (not default
!):
C:\Users\Suriyaa>docker-machine create --driver virtualbox default
Host already exists: "default"
C:\Users\Suriyaa>docker-machine create --driver virtualbox dev
Running pre-create checks...
(dev) You are using version 4.3.36r105129 of VirtualBox. If you encounter issues, you might want to upgrade to version 5 at https://www.virtualbox.org Creating machine...
(dev) Copying C:\Users\Suriyaa\.docker\machine\cache\boot2docker.iso to C:\Users\Suriyaa\.docker\machine\machines\dev\boot2docker.iso...
(dev) Creating VirtualBox VM...
(dev) Creating SSH key...
(dev) Starting the VM...
(dev) Check network to re-create if needed...
(dev) Waiting for an IP...
(dev) The host-only adapter is corrupted. Let's stop the VM, fix the host-only adapter and restart the VM
(dev) Windows might ask for the permission to configure a network adapter. Sometimes, such confirmation window is minimized in the taskbar.
(dev) Waiting for an IP...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env dev
C:\Users\Suriyaa>docker-machine env dev
SET DOCKER_TLS_VERIFY=1
SET DOCKER_HOST=tcp://192.168.99.101:2376
SET DOCKER_CERT_PATH=C:\Users\Suriyaa\.docker\machine\machines\dev
SET DOCKER_MACHINE_NAME=dev
REM Run this command to configure your shell:
REM FOR /f "tokens=*" %i IN ('docker-machine env dev') DO %i
C:\Users\Suriyaa>docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
default - virtualbox Error Unknown machine does not exist
dev - virtualbox Running tcp://192.168.99.101:2376 v1.10.3
C:\Users\Suriyaa>
After that, the docker-machine and the Quickstart Terminal should work.
Or I can run docker-machine create -d virtualbox --virtualbox-hostonly-cidr "192.168.99.2/24" default
(source: http://stackoverflow.com/a/34037073/5157221):
C:\Users\Suriyaa\Downloads>docker-machine create -d virtualbox --virtualbox-hostonly-cidr "192.168.99.2/24" default
Creating CA: C:\Users\Suriyaa\.docker\machine\certs\ca.pem
Creating client certificate: C:\Users\Suriyaa\.docker\machine\certs\cert.pem
Running pre-create checks...
(default) You are using version 4.3.36r105129 of VirtualBox. If you encounter issues, you might want to upgrade to version 5 at https://www.virtualbox.org
Creating machine...
(default) Copying C:\Users\Suriyaa\.docker\machine\cache\boot2docker.iso to C:\Users\Suriyaa\.docker\machine\machines\default\boot2docker.iso...
(default) Creating VirtualBox VM...
(default) Creating SSH key...
(default) Starting the VM...
(default) Check network to re-create if needed...
(default) Waiting for an IP...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env default
C:\Users\Suriyaa\Downloads>docker-machine env default
SET DOCKER_TLS_VERIFY=1
SET DOCKER_HOST=tcp://192.168.99.101:2376
SET DOCKER_CERT_PATH=C:\Users\Suriyaa\.docker\machine\machines\default
SET DOCKER_MACHINE_NAME=default
REM Run this command to configure your shell:
REM FOR /f "tokens=*" %i IN ('docker-machine env default') DO %i
C:\Users\Suriyaa\Downloads>docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
default - virtualbox Running tcp://192.168.99.101:2376 v1.10.3
C:\Users\Suriyaa\Downloads>
Check if everything works fine:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\Suriyaa>docker-machine restart default
Restarting "default"...
Waiting for SSH to be available...
Detecting the provisioner...
Restarted machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
C:\Users\Suriyaa>docker-machine env
SET DOCKER_TLS_VERIFY=1
SET DOCKER_HOST=tcp://192.168.99.101:2376
SET DOCKER_CERT_PATH=C:\Users\Suriyaa\.docker\machine\machines\default
SET DOCKER_MACHINE_NAME=default
REM Run this command to configure your shell:
REM FOR /f "tokens=*" %i IN ('docker-machine env') DO %i
C:\Users\Suriyaa>docker-machine restart default
Restarting "default"...
Waiting for SSH to be available...
Detecting the provisioner...
Restarted machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
:ok_hand: Perfect. Docker, the docker-machine
command and Kitematic works fine! :smile:
Every time I want to start Docker I must do this:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\Suriyaa>docker-machine regenerate-certs -f default
Regenerating TLS certificates
Waiting for SSH to be available...
Detecting the provisioner...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
C:\Users\Suriyaa>docker-machine start default
Starting "default"...
Machine "default" is already running.
C:\Users\Suriyaa>docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
default - virtualbox Running tcp://192.168.99.100:2376 v1.10.3
C:\Users\Suriyaa>
If I don't do this, I get error like this: https://forums.docker.com/t/an-error-occurred-trying-to-connect-read-tcp-192-168-99-100-2376-connection-reset-by-peer/8200!
Hello,
I tried to solve #1564 but I found some other problems.
When I click 'Quick Start Terminal' it works fine. But when I start the Kitematic software and create a container from a project I get the same problem like in #1564.
My problem
Here is the error I am getting:
I tried to fix the error
I run:
VirtualBox log
And I cat the log in
C:\Users\Suriyaa\.docker\machine\machines\default\default\Logs\VBox.log
:Version
I am using Windows 10 [x64-bit laptop] and VirtualBox 4.3.36 r105129 for Windows (downgraded from VirtualBox 5.0.14 r105127 for Windows).
Docker & Docker Toolbox verison:
Yours, Suriyaa Kudo :octocat: