Skip to content

CLI 19.03.1 does not support HTTP_PROXY/HTTPS_PROXY variables. #2027

@dmduggan

Description

@dmduggan

Description
CLI 19.03.1 does not support HTTP_PROXY/HTTPS_PROXY variables.

Steps to reproduce the issue:

  1. Set DOCKER_TLS_VERIFY=1, DOCKER_HOST, DOCKER_CERT_PATH, HTTP_PROXY, HTTPS_PROXY environment
  2. Run docker version

Describe the results you received:
Cannot connect to the Docker daemon at tcp://myswarm.com:2376. Is the docker daemon running?

Describe the results you expected:
Docker swarm commands to communicate over proxy.

Additional information you deem important (e.g. issue happens only occasionally):
Still works with 18.09.6.

Output of docker version:

PS C:\Projects> C:\ProgramData\chocolatey\bin\docker.exe version                                                                                                                                                                            Client:
 Version:           18.09.6
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        c89750f8
 Built:             06/09/2019 17:10:42
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.2
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       6247962
  Built:            Sun Feb 10 03:42:13 2019
  OS/Arch:          linux/amd64
  Experimental:     false
PS C:\Projects> & "C:\Program Files\Docker\Docker\Resources\bin\docker.exe" version                                                                                                                                                         Client: Docker Engine - Community
 Version:           19.03.1
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        74b1e89
 Built:             Thu Jul 25 21:17:08 2019
 OS/Arch:           windows/amd64
 Experimental:      false
Cannot connect to the Docker daemon at tcp://myswarm.com:2376. Is the docker daemon running?

Output of docker info:

Run with 18.09.6. Otherwise get the same error as with docker version.

PS C:\Projects> C:\ProgramData\chocolatey\bin\docker.exe  info                                                                                                                                                                              Containers: 133
 Running: 34
 Paused: 0
 Stopped: 99
Images: 48
Server Version: 18.09.2
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: splunk
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Authorization: docker-authz
 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: active
 NodeID: za7v4yld7uad9u50of9hngitv
 Is Manager: true
 ClusterID: rx9rxjifrru42hahwy77mm96k
 Managers: 3
 Nodes: 9
 Default Address Pool: x.0.0.0/8
 SubnetSize: 24
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 10
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
  Force Rotate: 0
 Autolock Managers: false
 Root Rotation In Progress: false
 Node Address: x.x.x.x
 Manager Addresses:
  x.x.x.x:2377
  x.x.x.x:2377
  x.x.x.x:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9754871865f7fe2f4e74d43e2fc7ccd237edcbce
runc version: 09c8266bf2fcf9519a651b04ae54c967b9ab86ec
init version: fec3683
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.4.0-1075-aws
Operating System: Ubuntu 16.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.508GiB
Name: lnx-i-01e8aecbd7de6ad35
ID: S5KB:GEQN:73U2:WDY6:QS2O:KH7E:ZXZ5:IVMO:BBEB:YYO6:N3FR:P2XK
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine

WARNING: No swap limit support

Additional environment details (AWS, VirtualBox, physical, etc.):
Swarm is in AWS

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions