Failed to clone the catalog from githubexit status 128

fatal: unable to access ‘https://github.com/rancher/rancher-catalog.git/’: Failed to connect to github.com port 443: Connection timed out
time=“2015-11-05T19:38:25Z” level=fatal msg="Failed to clone the catalog from githubexit status 128"
time=“2015-11-05T19:38:26Z” level=info msg="Starting Rancher Catalog service"
time=“2015-11-05T19:38:26Z” level=info msg="Cloning the catalog from github url https://github.com/rancher/rancher-catalog.git"
Cloning into ‘./DATA’…

    Rancher v0.44.0
    Cattle  v0.107.0
    User Interface v0.65.0
    Rancher Compose v0.5.1

I have another instance of Rancher, running the same version, and it seems to be working fine. Oh, and I can execute: git clone https://github.com/rancher/rancher-catalog.git on the host where the rancher server container is running.

I restarted Docker (1.8.2) and now the rancher server log is steaming this…

fatal: destination path ‘./DATA’ already exists and is not an empty directory.
time=“2015-11-05T19:51:51Z” level=fatal msg=“Failed to clone the catalog from githubexit status 128”

Please advise.

Firewall? The catalog service just calls essentially git clone https://github.com/rancher/rancher-catalog and the error message seems pretty clear that it tried to connect but never got a response.

what does this imply?
fatal: destination path ‘./DATA’ already exists and is not an empty directory.

This is again a git clone error, because the ./DATA folder was not empty when git tried to clone the repo.

But this is strange since rancher service does remove this folder and clones the catalog newly every time you restart it.

Did you see this error after you restarted Docker? Or any specific steps that lead you to this error?

I did restart docker along the way. It’s likely a firewall issue, as @vincent sugggested. I was able to pass in a proxy env varible and it works now. This is just a problem I didn’t have before 44, that I know of. And I suppose the problem was on my end. :grin: