When adding a custom catalog the clone also times out, presumably because the host is not in no_proxy. The setting there also doesn’t appear to stick as a result.
Would someone be able to confirm if http_proxy and no_proxy for this operation are inherited from the docker service proxy configuration? Will a git clone work if the proxy is configured correctly? For github.com if this is supported we have HTTP_PROXY set in /etc/systemd/system/docker.service.d/http-proxy.conf but does not appear to be used with this operation.
I run one rancher server instance in a lab where a proxy is required most of the time. I couldn’t get the catalog to load and when I passed in the http_proxy env variable it worked as I remember. Now I always start that instance and pass in http_proxy. So apparently, it won’t hurt anything.
