Cannot install connector on Broadcom hardened VM docker when behind proxy

Products

• Symantec ZTNA

Issue/Introduction

ZTNA Admin using VMware-Based Connector Image.

When trying to run the docker run command to setup the ZTNA connector behind a Cloud SWG proxy, the install fails with an 'unable to find image' error as shown below:

Unable to find image 'xxxxx' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.

When not using a proxy, all works fine.

Tried using the proxy environmental variable "HTTP_proxy" as well as changing proxy.sh and creating ~/.docker/daemon.json - all without success.

How can we enable proxy support on the ZTNA docker VM? The action fails because the docker is not using the proxy settings.

 

Environment

ZTNA connector on Broadcom hardened VM.

ALl traffic should go to a proxy (in our case the Cloud SWG Proxy at 199.19.250.205:80)

 

Cause

Misconfigured proxy configuration on docker VM.

Resolution

If your organization uses a proxy server to connect to the internet, you will need to configure the Docker daemon to use the proxy server. The daemon uses a proxy server to access images stored on Docker Hub and other registries, and to reach other nodes in a Docker swarm.

With the CLoud SWG proxy used in the above setup, the ZTNA admin created /etc/docker/daemon.json and added

{
  "proxies": {
    "http-proxy": "http://199.19.250.205:80",
    "https-proxy": "http://199.19.250.205:80",
    "no-proxy": 127.0.0.0/8"
  }
}

Once the service restart for docker was performed, all communication started using the proxy as expected and ZTNA connector installed successfully.