Part of the build is the final push - Docker 1.9 and older didn't have an important optimization that avoided pushing binaries to the registry that already existed. But as Tomas noted, local storage plays a huge role on builds.
On Thu, Apr 21, 2016 at 8:03 AM, Candide Kemmler <[email protected]> wrote: > Thanks Tomas, > > But, really what's the reason why it is so slow? Everything happens locally > to the machine and my local docker operations are usually very fast when I'm > working from my laptop. Why so is everything suddenly so slow when it > executes on OpenShift? > >> On 21 Apr 2016, at 10:47, Tomáš Kukrál <[email protected]> wrote: >> >> Hi, >> using slow docker storage could be the reason. I'd also suggest you to >> examine CPU usage because `docker push` is quite CPU gluttonous. >> >> tom >> >> On 04-21 09:04, Candide Kemmler wrote: >>> I'm always surprised at the time it takes for a new image to be pushed to >>> the local registry. I would expect this to be fast, but it's really not. >>> >>> That said I haven't set up docker storage to use a separate block device as >>> is recommended because my hosting service (vultr) doesn't have them (at >>> least in my region)... Could that explain it? >>> >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users > > > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
