Skip to content
This repository has been archived by the owner on Jun 11, 2021. It is now read-only.

Unable to Fetch Restcomm Repo #1772

Closed
bilal966 opened this issue Jun 19, 2016 · 8 comments
Closed

Unable to Fetch Restcomm Repo #1772

bilal966 opened this issue Jun 19, 2016 · 8 comments

Comments

@bilal966
Copy link

Expected behavior

Actual behavior

Information about the Issue

Steps to reproduce the behavior

  1. Select Repo on Docker (restcomm)
  2. Select Tag "Stable"
  3. Click on Create button

Output:
Network timed out while trying to connect to https://index.docker.io/v1/repositories/restcomm/restcomm/images. You may want to check your internet connection or if you are behind a proxy

@ErrolSayre
Copy link

I'm getting this same error trying to install mattermost.

@FrenchBen
Copy link
Contributor

@bilal966 Not sure what you searched for or clicked on - I followed the exact steps that you provided and get a proper download:
restcomm

@FrenchBen
Copy link
Contributor

@ErrolSayre Can you provide a link to the Docker Hub image you're trying to download?

@ErrolSayre
Copy link

I'm away from that box, but I was trying to install mattermost-preview and got a similar error message.

@banesto
Copy link

banesto commented Jun 25, 2016

I have the same issue with Docker 2 beta. Strangely enough, when I connect to my company's VPN then it's ok and I can pull images. It's some sort of networking problem, but I'm not able to tell if the root of issue is within IPS, my router AirPort, Mac or Docker. Maybe https://index.docker.io/v1/repositories/ is running on some non-standart port or something?

And it's exactly the same error when pulling image in terminal or from Kitematic

@FrenchBen
Copy link
Contributor

@banesto if changing network allows you to pull, then it's more than likely related to your own network.

@banesto
Copy link

banesto commented Jun 29, 2016

@FrenchBen Yes, but the issue still persists on a computer without any VPN installed and there's no clear hint on how to resolve this or what is the blocker.

@FrenchBen
Copy link
Contributor

@banesto Unfortunately this is outside of the scope of Kitematic, as it's related to your particular network setup more than the tool itself.
I would start by confirming that you cannot pull outside of the VM, then inside of the VM and try normal network-related stuff to gain some knowledge as to why your network is blocking this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants