I’m following the docs on running Rancher behind a web proxy and starting it like this:
docker run -d --restart=unless-stopped -p 80:80 -p 443:443 -e HTTP_PROXY="http://myproxy.example.com:3128" -e HTTPS_PROXY="http://myproxy.example.com:3128" -e NO_PROXY="localhost,127.0.0.1,0.0.0.0,<localsubnet>,mydomain.example.com" -v /opt/rancher:/var/lib/rancher rancher/rancher:latest --no-cacerts
Also, I’m installing rancher on a separate docker instance, not within an existing kubernetes cluster.
However, running this way either prevents me from importing a cluster (stays in pending) or causes an existing cluster to go unavailable.
I’ve checked the proxy logs and I’m not seeing anywhere that traffic is being blocked. Any thing else I can check or specific logs to look for?
We’re behind a corporate firewall and our only access out to the internet is via proxy. The Docker proxy allows me to pull Rancher down, but without the proxy running for Rancher, access to catalogs is broken.