Docker push takes a lot of time

I have a deployment setup with Docker that works as follows:

  • Create an image on my dev machine via a Docker file
  • Click image into registry (I tried both Docker Hub and Quay.io)
  • Pull this image to the deployment server and restart the container.

I would like to take these steps as quickly as possible, but they take a very long time. Even for an image of a modest size (750MiB, including standard ubuntuand friends), after a small modification, deployment takes 17 minutes . I optimized the order of the elements in mine Dockerfile, so it actually picks up cached images most of the time. It does not seem to matter.

The main culprit is the move docker push. Both the Docker Hub and Quay.io require an unrealistically long time to create images. In one of the simple tests, I performed docker pushtwo times ago, so that all previous images are already in the registry. Therefore, I see only the following lines:

...
bf84c1d841244f: Image already pushed, skipping
...

But if I press the time, the performance is terrifying. Clicking Quay.io takes 3.5 minutes when all the images are already on the server! Clicking on the Docker Hub takes about 12 minutes !

There is clearly something wrong there, since many people use Docker in production, these times are exactly the opposite of continuous delivery.

? ​​? - ?

Docker Mac OS X.

+4
3

. .

, , Google Container Engine Amazon Container Service, , .

+1

, . , , . , . , Docker Hub (, ).

, , - , Linux, boot2docker docker-machine, , .

+1

: , , "docker push", - . - , SSD ( , ~ 500 + / , ). , push docker, , , . , - " ". , , , (, -, - URI push, - ).

, , , , push. , . : - , .

, () OP. , , . , , . URI / - , //.

0

Source: https://habr.com/ru/post/1613505/


All Articles