Expected behavior
- pull image behind corporate proxy servers.
- run containers, and these containers need download patch “yum update” hehind corporate proxy servers.
Actual behavior
$ docker pull busybox
Using default tag: latest
Pulling repository docker.io/library/busybox
Error while pulling image: Get https://index.docker.io/v1/repositories/library/busybox/images: dial tcp: lookup index.docker.io on 192.168.64.1:53: no such host
Information
- the output of:
pinata diagnose -u
on OSX
$ pinata diagnose -u
OS X: version 10.11.3 (build: 15D21)
Docker.app: version v1.11.0-beta6
Running diagnostic tests:
[OK] docker-cli
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160414-144824.tar.gz.
Your unique id in bugsnag is: 50A16E2F-27ED-4619-8C52-5E64D48D2CF5
Please quote this in all correspondence.
- `DockerDebugInfo.ps1` using Powershell on Windows
-
a reproducible case if this is a bug, Dockerfiles FTW
docker pull busybox
-
page URL if this is a docs issue or the name of a man page
-
host distribution and version ( OSX 10.10.x, OSX 10.11.x, Windows, etc )
10.11.3
Steps to reproduce the behavior
$ docker pull busybox
Using default tag: latest
Pulling repository docker.io/library/busybox
Error while pulling image: Get https://index.docker.io/v1/repositories/library/busybox/images: dial tcp: lookup index.docker.io on 192.168.64.1:53: no such host