Hi all,
I am getting a timeout error whilst trying to push my docker image to the servers. I can use the docker login command to login to docker.synapse.or, but cant seem to push my image at the moment.
One of my layers gets stuck, and continuously tries to reconnect before timing out.
More than likely an issue on my end, but just wondering if anyone else is having this problem.
Here is an output of what I get whilst trying to push the image.
While it is trying to connect
```
root@ethan-ThinkPad-E460:/home/ethan/DREAM# docker push docker.synapse.org/syn8112226/preprocessing_test
The push refers to a repository [docker.synapse.org/syn8112226/preprocessing_test]
d2e1549bf395: Preparing
754d0d3706a4: Preparing
9533cb8617a4: Layer already exists
426dd561793f: Layer already exists
eafecfffe147: Layer already exists
ae9dd43fc806: Layer already exists
31d5ab6973dc: Layer already exists
a02aed6ff452: Layer already exists
10f309302a86: Layer already exists
0b0553c21fdb: Layer already exists
9fd713a7e7e9: Retrying in 5 seconds
3672547b1dd1: Pushing 5.543 MB/127.7 MB
068f48a4f5bd: Pushing 5.543 MB/205.9 MB
e281a8358a7a: Pushing 7.22 MB/55.06 MB
9c40fd641459: Pushing 13.91 MB/104.8 MB
161f1ce2c8bc: Waiting
cc10d3105ed8: Waiting
7360106cda72: Waiting
ec96d31f8eaf: Waiting
e3ac10d00c60: Waiting
2c2153fbd032: Waiting
d9a069c1d0fc: Waiting
a5eb0fc1decb: Waiting
b2ac5371e0f2: Waiting
142a601d9793: Waiting
```
Then after it can't reconnect,
```
net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
```
Any help would be gratly appreciated :)
Created by Ethan Goan ethan.goan Thanks for the help everyone, I have been able to push my images. I tried submitting from my home network, but it really isn't capable of uploading anything of significant size, so I just used my universities internet and it all worked not a problem.
@ethan.goan, sorry you've had these issues. I have not heard from many others having similar issues, however, @fustbariclation did have a similar problem early on. He may wish to comment with greater detail but I believe the issue was the bandwidth from his location to our Docker registry (which runs in Amazon's eastern U.S. region). I recall he resolved the issue by using Docker on a server he provisioned from a cloud provider having greater connectivity to the internet at large. There are many such providers but an obvious (and low cost) choice is Amazon Elastic Compute Cloud.
Hope this helps. Hi Ethan,
The suggestions from @davecg and @jyu are correct. Can you now push to Synapse?
Thanks! also helps to check the size of your image (view it from "docker images" command)
there is a 10GB limit for image size in this challenge I've only had this happen to me when Synapse has been shut down for maintenance.
Assuming that's not the case, I would try restarting the docker service and maybe try uploading from a different network.