Documentation of proxy configuration via config.json does not match the implementation

[somcsel]

Problem description

Docker CLI fails to parse its config.json if it contains a proxy configuration object based on the format shown in the documentation:

$ docker version
WARNING: Error loading config file: /home/sl/.docker/config.json - json: cannot unmarshal string into Go struct field ConfigFile.proxies of type configfile.ProxyConfig

Problem location

• I saw a problem on the following URL:
  https://docs.docker.com/engine/userguide/networking/#use-a-proxy-server-with-containers

Project version(s) affected

17.09.0-ce onwards (stable)
17.07.0-ce onwards (edge)

Suggestions for a fix

A suggested fix is uploaded as PR #4687.

The documented JSON proxy configuration structure does not match the implementation in docker/cli#93. The JSON strucuture requires an intermediate object named default in between proxies and the servers. This is because, in addition to the default proxy servers, the cli implementation makes it possible to specify the proxies to use when connnecting to a specific docker daemon, e.g.

    {
      "proxies":
      {
        "default":
        {
          "httpProxy": "http://127.0.0.1:3001",
          "noProxy": "*.test.example.com,.example2.com"
        },
        "tcp://example.docker.com:2376":
        {
          "httpProxy": "http://proxy.intra.mycorp.com:8080",
          "httpsProxy": "http://proxy.intra.mycorp.com:8080",
          "noProxy": "*.intra.mycorp.com"
        }
      }
    }

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked