Docker Community Forums

Share and learn in the Docker community.

Issue when docker pooling an image

(Geletok) #1


I am trying to run docker container on Windows 8.1. When I tried to run
hello-world for example, I got an error. See below snipped form console:

PS C:\Program Files\Docker Toolbox\kitematic> docker run hello-world

Unable to find image ‘hello-world:latest’ locally
Pulling repository
Network timed out while trying to connect to You may want to check your internet connection or if you are behind a proxy.

Then I checked whether mentioned URL is accessible from the console where I run the container:

PS C:\Program Files\Docker Toolbox\kitematic> curl

StatusCode : 200
StatusDescription : OK
Content : [{“checksum”: “”, “id”: “3f12c794407e68e515ba7f473a744e748ac8a827a2ea8b33855dec564238b2e5”},
{“checksum”: “”, “id”: “975b84d108f1024953937167506c2935a081c8c55ae9e9f7b7deee118605367f”},
{“checksum”: “”…
RawContent : HTTP/1.1 200 OK
Transfer-Encoding: chunked
Vary: Cookie
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=31536000
Content-Type: application…
Forms : {}
Headers : {[Transfer-Encoding, chunked], [Vary, Cookie], [X-Docker-Endpoints,],
[X-Frame-Options, SAMEORIGIN]…}
Images : {}
InputFields : {}
Links : {}
ParsedHtml : mshtml.HTMLDocumentClass
RawContentLength : 1564

So it seems all with the connection is fine and URL is accessible.

Here is some info about docker version.

Version: 1.8.3
API version: 1.20
Go version: go1.4.2
Git commit: f4bf5c7
Built: Mon Oct 12 18:01:15 UTC 2015
OS/Arch: windows/amd64

Version: 1.8.2
API version: 1.20
Go version: go1.4.2
Git commit: 0a8c2e3
Built: Thu Sep 10 19:10:10 UTC 2015
OS/Arch: linux/amd64

Host I am working on is behind proxy set via environment variables HTTP_PROXY and HTTPS_PROXY.

Can someone help me bring docker working?

Thank you and Regards

(Jeff Anderson) #2


Your docker daemon is actually running inside a virtual machine. You can ssh to that VM by typing docker-machine ssh default. To set the proxy variables at this point, you can set them by putting them inside the /var/lib/boot2docker/profile file. A reboot of the VM should make your changes take effect.

This change only affects processes running directly on the boot2docker host. Containers are still have their own isolated environment, and will need to have their environment variables set at runtime. You can set those with the -e option to the docker run command.

You’ll need to set it if you use the ‘docker build’ feature as well. The quick fix for getting your Dockerfile to build inside a network with a proxy is to simply set HTTP_PROXY, HTTPS_PROXY, and NO_PROXY inside the Dockerfile using the ENV directive.