# Wann und wie Docker upgraden?

**URL:** <https://meta.discourse.org/t/when-to-upgrade-docker-and-how/86989>\
**Category:** Support\
**Created:** [8. Mai 2018 um 11:40 UTC](https://meta.discourse.org/t/when-to-upgrade-docker-and-how/86989 "2018-05-08T11:40:02Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![tophee](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tophee/32/73406_2.png) [@tophee](https://meta.discourse.org/u/tophee)\
**Post date:** [8. Mai 2018 um 11:40 UTC](https://meta.discourse.org/t/when-to-upgrade-docker-and-how/86989/1 "2018-05-08T11:40:02Z")

</div>

Continuing the discussion from [Docker using a lot of CPU](https://meta.discourse.org/t/docker-using-a-lot-of-cpu/76788/6):

> [@Docker using a lot of CPU](https://meta.discourse.org/t/docker-using-a-lot-of-cpu/76788/6):
>
> \> 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.

I had made a mental not that I’ll eventuall need to allow my instance to upgrade docker again, after downgrading because of that bug, but I’m not sure when I should do that nor how I do it without breaking stuff… Or do I need to do anything?

---

_[View the full topic](https://meta.discourse.org/t/when-to-upgrade-docker-and-how/86989)._