Answer the question
In order to leave comments, you need to log in
How to run docker?
installed docker-toolbox on windows 10
how to start docker now if errors occur and hangs on "Waiting for an IP ..."?
Error checking TLS connection: ssh command error:
command : ip addr show
err : exit status 255
output :
Error checking TLS connection: ssh command error:
command : ip addr show
err : exit status 255
output :
## .
## ## ## ==
## ## ## ## ## ===
/"""""""""""""""""\___/ ===
~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ / ===- ~~~
\______ o __/
\ \ __/
\____\_______/
Error getting IP address: ssh command error:
command : ip addr show
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
Start interactive shell
[email protected] MINGW64 /d/progs/Docker Toolbox
$ docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
default * virtualbox Running Unknown ssh command error:
command : ip addr show
err : exit status 255
output :
[email protected] MINGW64 /d/progs/Docker Toolbox
$ docker-machine create box
Running pre-create checks...
Creating machine...
(box) Copying C:\Users\asyal\.docker\machine\cache\boot2docker.iso to C:\Users\asyal\.docker\machine\machines\box\boot2docker.iso...
(box) Creating VirtualBox VM...
(box) Creating SSH key...
(box) Starting the VM...
(box) Check network to re-create if needed...
(box) Waiting for an IP...
Error creating machine: Error in driver during machine creation: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded
[email protected] MINGW64 /d/progs/Docker Toolbox
$ docker-machine inspect default
{
"ConfigVersion": 3,
"Driver": {
"IPAddress": "",
"MachineName": "default",
"SSHUser": "docker",
"SSHPort": 0,
"SSHKeyPath": "",
"StorePath": "C:\\Users\\asyal\\.docker\\machine",
"SwarmMaster": false,
"SwarmHost": "tcp://0.0.0.0:3376",
"SwarmDiscovery": "",
"VBoxManager": {},
"HostInterfaces": {},
"CPU": 1,
"Memory": 1024,
"DiskSize": 20000,
"NatNicType": "82540EM",
"Boot2DockerURL": "",
"Boot2DockerImportVM": "",
"HostDNSResolver": false,
"HostOnlyCIDR": "192.168.99.1/24",
"HostOnlyNicType": "82540EM",
"HostOnlyPromiscMode": "deny",
"UIType": "headless",
"HostOnlyNoDHCP": false,
"NoShare": false,
"DNSProxy": true,
"NoVTXCheck": false,
"ShareFolder": ""
},
"DriverName": "virtualbox",
"HostOptions": {
"Driver": "",
"Memory": 0,
"Disk": 0,
"EngineOptions": {
"ArbitraryFlags": [],
"Dns": null,
"GraphDir": "",
"Env": [],
"Ipv6": false,
"InsecureRegistry": [],
"Labels": [],
"LogLevel": "",
"StorageDriver": "",
"SelinuxEnabled": false,
"TlsVerify": true,
"RegistryMirror": [],
"InstallURL": "https://get.docker.com"
},
"SwarmOptions": {
"IsSwarm": false,
"Address": "",
"Discovery": "",
"Agent": false,
"Master": false,
"Host": "tcp://0.0.0.0:3376",
"Image": "swarm:latest",
"Strategy": "spread",
"Heartbeat": 0,
"Overcommit": 0,
"ArbitraryFlags": [],
"ArbitraryJoinFlags": [],
"Env": null,
"IsExperimental": false
},
"AuthOptions": {
"CertDir": "C:\\Users\\asyal\\.docker\\machine\\certs",
"CaCertPath": "C:\\Users\\asyal\\.docker\\machine\\certs\\ca.pem",
"CaPrivateKeyPath": "C:\\Users\\asyal\\.docker\\machine\\certs\\ca-key.pem",
"CaCertRemotePath": "",
"ServerCertPath": "C:\\Users\\asyal\\.docker\\machine\\machines\\default\\server.pem",
"ServerKeyPath": "C:\\Users\\asyal\\.docker\\machine\\machines\\default\\server-key.pem",
"ClientKeyPath": "C:\\Users\\asyal\\.docker\\machine\\certs\\key.pem",
"ServerCertRemotePath": "",
"ServerKeyRemotePath": "",
"ClientCertPath": "C:\\Users\\asyal\\.docker\\machine\\certs\\cert.pem",
"ServerCertSANs": [],
"StorePath": "C:\\Users\\asyal\\.docker\\machine\\machines\\default"
}
},
"Name": "default"
}
[email protected] MINGW64 /d/progs/Docker Toolbox
$ docker run hello-world
D:\progs\Docker Toolbox\docker.exe: error during connect: Post http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.40/containers/create: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.
See 'D:\progs\Docker Toolbox\docker.exe run --help'.
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question