I’m just getting started with Docker and attempted to follow the install instructions to the T.
Win7 x64
Virtualization enabled & tested with the MS tool
Never had any docker tools installed before today.
The only thing I installed was the docker toolbox
Attempt to run hello world failed.
$ docker run hello-wolrd
An error occurred trying to connect: XXXXXXXXXXX_2375/v1.21/containers/create: dial tcp 127.0.tEx tcp: No connection could be made because the target machine actively refused it.
I also read this where the user has a similar issue.
I ran docker version … RESULTs
$ docker version
Client:
Version: 1.9.0
API version: 1.21
Go version: go1.4.3
Git commit: 76d6bc9
Built: Tue Nov 3 19:20:09 UTC 2015
OS/Arch: windows/amd64
An error occurred trying to connect: Get XXXXX_ocalhost:2375/v1.21/version: dial tcp 127.0.0.1:2375: ConnectEx tcp: No connection could be made because the target machine actively refused it.
Any advice would be hugely appreciated. Based on the output it appears the server is not running, just the client. I don’t think I missed any steps. I’m just barely getting started.
Generally this error happens if your shell does not have the environment variables that tell your docker client how to connect to the docker service.
It is entirely possible that something went wrong during your first installation attempt, and the virtualbox docker vm wasn’t 100% set up and running, causing there to be nothing to configure your shell for in the quickstart terminal.
This exception message says you’re trying to connect to the same host ( 127.0.0.1 ), while you’re stating that your server is running on a different host. This 127.0.0.1 represents a ‘loopback’ . It allows the computer to communicate with itself via network protocol .
Dns.GetHostEntry(IPAddress.Loopback).HostName returns the host name of your machine. When you pass a host name to TcpClient , it will resolve it to one or more IP addresses using Dns.GetHostAddresses(hostName) . This includes the public and local IP addresses of your machine (e.g. 192.168.12.10), but not 127.0.0.1 (loopback address). So your client is trying to connect to any of the non-loopback addresses of your machine, while your server is listening only on the loopback address . So, no connection can be established. The solution to this problem is that connect to the same end point your server is listening on.