Pushing a Docker image to a private Docker warehouse suddenly takes an extremely long time

Environments Linux
,
1

There seems to be something wrong with the build environment of travis, In the past few days, I suddenly discovered that my docker image can no longer be pushed to the docker warehouse deployed by my private cloud server!,it takes more than an hour to push the image in a MB unit to my privatized deployed Docker warehouse,It seems to be the server network,It takes over an hour to push a Docker image no more than 1GB to my privatized docker repository,My private Docker warehouse doesn’t have any network issues, and I found only Travis Ci did,The execution time of a CI dragged from about 7 minutes to over an hour, which prevented me from using Travis Ci

url: https://travis-ci.com/github/DataPipelineInc/dp-customer-dashboard/builds/198749006

2

travis
travis1155×561 76.6 KB

3

Hey @collides,

I would take a read:

4

travis
travis1518×951 43.3 KB

5

hey @Montana,
I am using a privatized deployed docker repository, I don’t understand what does this have to do with me?

1 Like
6

Testing network speed with Speedtest CLI shows that there are no speed limitations from Travis’ side:

   Speedtest by Ookla
     Server: Pavlov Media - Atlanta, GA (id = 5296)
        ISP: Google Cloud
    Latency:    10.82 ms   (0.06 ms jitter)
   Download:   883.20 Mbps (data used: 952.5 MB)                               
     Upload:   310.90 Mbps (data used: 362.6 MB)                               
Packet Loss:     0.6%
 Result URL: https://www.speedtest.net/result/c/3e207307-f250-4195-93b2-522f8110e592

So check the network route to your specific server, e.g. with traceroute and netperf.

Depending on the software you use, there may be other limitations – e.g. if your server is commercial software, its license may have expired or something.

7

Hi @native-api , Thank you very much for answering my question

It’s slowed down from the beginning of November and I can’t figure out why. I have checked all the problem points That I can think of. Although I can’t find the point of the problem, from the perspective of the network phenomenon, it should be the reason why the American server is slow to access the Chinese server

Because I can’t find the problem, I can only consider migrating from Travis to the CI server in China at present

8

If you can’t figure the problem out on your own, you may have a network specialist take a look at it.

9

I don’t understand, nothing has changed, and all of a sudden it’s successful again, It’s too puzzling

url: https://travis-ci.com/github/DataPipelineInc/dp-customer-dashboard/builds/202949634