Cannot run docker hello-world behind a proxy with docker toolbox

Docker Desktop
,
1
  • Issue type: cannot connect to Docker
    C:\Program Files\Docker Toolbox\docker.exe: Error response from daemon: Get https://registry-1.docker.io/v2/: proxyconnect tcp: EOF.
  • **OS Version/build:**Windows 10 Enterprise 2016
  • App version (docker toolbox):

docker version
Client:
Version: 18.03.0-ce
API version: 1.37
Go version: go1.9.4
Git commit: 0520e24302
Built: Fri Mar 23 08:31:36 2018
OS/Arch: windows/amd64
Experimental: false
Orchestrator: swarm

Server: Docker Engine - Community
Engine:
Version: 18.09.1
API version: 1.39 (minimum version 1.12)
Go version: go1.10.6
Git commit: 4c52b90
Built: Wed Jan 9 19:41:57 2019
OS/Arch: linux/amd64
Experimental: false

  • Steps to reproduce:

-behind a corporate proxy:

  • start the service (click docker toolbox which starts start.sh)
  • create the container:
    docker-machine create -d virtualbox --engine-env HTTP_PROXY=http://proxy.com --engine-env HTTPS_PROXY=https://proxy.com --engine-env NO_PROXY=192.168.99.100 default
  • run hello world: docker run hello-world

Things i tried so far
configure ENV variables for http_proxy in windows and containter
change DNS resolv both in windows and container
try to wget https://registry-1.docker.io/v2/ both from Windows (ok), and from container (it fails connection reset by server)

2

I went one step beyond, uninstalled Toolbox, installed it again, switched back and forth the proxy, and now this is how it looks:

c:\work\tmp>docker run hello-world
Unable to find image ‘hello-world:latest’ locally
latest: Pulling from library/hello-world
1b930d010525: Pulling fs layer
docker: error pulling image configuration: Get https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/fc/fce289e99eb9bca977dae136fbe2a82b6b7d4c372474c9235adc1741675f587e/data?verify=1548321649-3S7xuqHOlaWvEfoUVIdCpGPV3e8%3D: EOF.

I read through all the stack of messages for this error to no avail

3

this morning i was able to login to docker and ./docker/config.json was filled with authentication data, but this evening all docker commands fail again unable to access index.docker.io
Is it normal to experience this back and forth behaviour?