Trouble with outbound networking connection with Dockerhub
Linode
Linode Staff
We are generating docker images on this server and uploading these to Dockerhub. The size of upload is in range of 100-500 MB. Download from Dockerhub is fast and we have seen no issues.
These upload are behaving irritatingly. Sometimes, it's very fast - within few seconds, but most of time it's taking around 20-30 Minutes.
Upload has been slow since over the last 15 days. Earlier it used to be fast.
Please let us know if this is due to some network limit on our Linode instance or what can be done to fix the issue.
1 Reply
watrick
Linode Staff
Hi there,
We don't do any rate limiting for outbound traffic. If you go over your Network Transfer Quota, you would be invoiced at a rate of $0.02 for each GB over in your month. We have a guide that covers this, and everything else you may want to know about Network Transfer Quota
When it comes to a spotty connection like this, we'd like to get an MTR report that shows the connection path between your Linode and the destination. Ideally, we'd like to have one in both directions, but in this case, that would not be possible, unless you have access to the Dockerhub server.
I attempted to look up what the IP would be for you, but based on this post on the Docker Community Forum, that looks like it may be harder than expected:
https://forums.docker.com/t/docker-registry-public-ip-addresses/10013
Based on this, you will need to figure out the current IP address by running this curl command:
curl -v https://index.docker.io:443
I just ran this and got an IP of 35.153.91.114. I would suggest checking this before performing the next step.
Once you have the IP address, please run this MTR command:
mtr -rwbzc100 $DockerHubIP
Please consult our doc on MTR Reports if you're unfamiliar with them.
Because the DockerHub IP address may change over time, this sudden change in upload times could be caused by routing issues to a new IP address. You'll be able to confirm or dismiss this theory through an MTR report by looking to see if there's any packet loss.
If you do see a routing issue in your MTR report, I would recommend reaching out to the ISP that is responsible for the router that is affecting connectivity.
Regards,
Pat Woods
Linode Support Team