# Docker push much slower as of ~11/17?

**URL:** <https://discuss.circleci.com/t/docker-push-much-slower-as-of-11-17/811>\
**Category:** Build Environment\
**Tags:** docker\
**Created:** [November 29, 2015, 9:51pm UTC](https://discuss.circleci.com/t/docker-push-much-slower-as-of-11-17/811 "2015-11-29T21:51:32Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![mkscrg](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/mkscrg/32/390_2.png) [@mkscrg](https://discuss.circleci.com/u/mkscrg)\
**Post date:** [November 29, 2015, 9:51pm UTC](https://discuss.circleci.com/t/docker-push-much-slower-as-of-11-17/811/1 "2015-11-29T21:51:32Z")

</div>

We noticed about a week ago that Docker image pushes to [Quay.io](http://Quay.io) have gotten a lot slower. Pushes to Quay are still quick from our own EC2 machines. Did something change on Circle’s side?

---

<div class="post-metadata">

**Author:** ![alexey](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/alexey/32/42_2.png) [@alexey](https://discuss.circleci.com/u/alexey)\
**Post date:** [November 30, 2015, 2:46pm UTC](https://discuss.circleci.com/t/docker-push-much-slower-as-of-11-17/811/2 "2015-11-30T14:46:39Z")

</div>

What kind of data transfer speed are you getting now? It would also be great to know what was the bandwidth you were seeing previously.

---

<div class="post-metadata">

**Author:** ![mkscrg](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/mkscrg/32/390_2.png) [@mkscrg](https://discuss.circleci.com/u/mkscrg)\
**Post date:** [November 30, 2015, 5:55pm UTC](https://discuss.circleci.com/t/docker-push-much-slower-as-of-11-17/811/3 "2015-11-30T17:55:23Z")

</div>

`docker push` doesn’t report bandwidth, so it’s hard to tell! We didn’t have any formal benchmarks setup before this issue, and haven’t made any since. From builds before and after the slowdown, I can see that `docker push` used to take ~1m and now takes ~5m. In both cases we’re only pushing ~15MB to Quay.

---

<div class="post-metadata">

**Author:** ![alexey](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/alexey/32/42_2.png) [@alexey](https://discuss.circleci.com/u/alexey)\
**Post date:** [December 1, 2015, 4:39pm UTC](https://discuss.circleci.com/t/docker-push-much-slower-as-of-11-17/811/4 "2015-12-01T16:39:09Z")

</div>

I am afraid this might be a question for [Quay.io](http://Quay.io) support. We haven’t observed any network issues recently, and so we don’t think this is directly related to any of our actions. Thank you for your understanding.

---

<div class="post-metadata">

**Author:** ![alikhan\_io](https://avatars.discourse-cdn.com/v4/letter/a/5e9695/32.png) [@alikhan\_io](https://discuss.circleci.com/u/alikhan_io)\
**Post date:** [January 12, 2016, 4:47pm UTC](https://discuss.circleci.com/t/docker-push-much-slower-as-of-11-17/811/5 "2016-01-12T16:47:47Z")

</div>

Late answer but I noticed in debugging CircleCI is using Docker v1.8. In Docker 1.9 there is a fix for the buffering to disk that greatly speeds up pushes. I filed a ticket pointing this out and hoping they default upgrade.

In the mean time I’m trying to figure out how to script a forced upgrade to docker 1.9

---

<div class="post-metadata">

**Author:** ![alexey](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/alexey/32/42_2.png) [@alexey](https://discuss.circleci.com/u/alexey)\
**Post date:** [January 13, 2016, 9:29am UTC](https://discuss.circleci.com/t/docker-push-much-slower-as-of-11-17/811/6 "2016-01-13T09:29:49Z")

</div>

[This post](https://discuss.circleci.com/t/docker-1-9-1-is-available/1009) might be helpful.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [June 18, 2018, 11:37am UTC](https://discuss.circleci.com/t/docker-push-much-slower-as-of-11-17/811/7 "2018-06-18T11:37:41Z")

</div>


