# Docker using a lot of CPU

**URL:** https://meta.discourse.org/t/docker-using-a-lot-of-cpu/76788
**Category:** Self-hosting
**Tags:** server-resources
**Created:** [26 Dicembre 2017, 10:37pm UTC](https://meta.discourse.org/t/docker-using-a-lot-of-cpu/76788 "2017-12-26T22:37:01Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [26 Dicembre 2017, 10:57pm UTC](https://meta.discourse.org/t/docker-using-a-lot-of-cpu/76788/6 "2017-12-26T22:57:15Z")

</div>

> [@tophee](#):
>
> How did I get that one? I don’t intentionally install experimental versions. All I do is apt-get upgrade from time to time…

You probably got the “experimental” version because that’s what everyone gets if they initially installed via `curl https://get.docker.com | sh`. You have to change `/etc/apt/sources.list.d/docker.list` to track the `stable` repo rather than `edge` or whatever the default is.

> [@tophee](#):
>
> Looks like one should be rather conservative in upgrading docker?

Being conservative in upgrading docker isn’t even enough; we follow that policy (still on 17.06), and we _still_ got hit by [a ripper of a bug](https://github.com/moby/moby/issues/35757) that exists in all versions from 17.06 to 17.11 (and, by the glacial pace at which the PR is moving, will probably be in 18.01 or whatever the next release will be).

Basically, Docker’s gonna Docker, and all we can do is hang on for the ride and try and dodge the worst of the low-hanging tree branches.

---

_[View the full topic](https://meta.discourse.org/t/docker-using-a-lot-of-cpu/76788)._