# Discourse web interface becomes unresponsive a few minutes after starting

**URL:** https://meta.discourse.org/t/discourse-web-interface-becomes-unresponsive-a-few-minutes-after-starting/76643
**Category:** Self-hosting
**Created:** [December 22, 2017, 9:05pm UTC](https://meta.discourse.org/t/discourse-web-interface-becomes-unresponsive-a-few-minutes-after-starting/76643 "2017-12-22T21:05:56Z")
**Posts on this page:** 1
**Showing post:** 14

<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: [December 24, 2017, 2:27am UTC](https://meta.discourse.org/t/discourse-web-interface-becomes-unresponsive-a-few-minutes-after-starting/76643/14 "2017-12-24T02:27:43Z")

</div>

Ladies, Gentlemen, and Small Furry Creatures From Alpha Centauri, I present to you: [the Docker bug that has been causing all the angst](https://github.com/moby/moby/issues/35865). I got a reliable repro, and verified that only `docker-ce` 17.11 is impacted. Hopefully, Docker will fix the bug sooner or later, but until then, the recommended workaround is to downgrade Docker to a working version, as follows:

1. **Stop and delete all running containers**. In addition to this bug, Docker also changed some _other_ things in the way that containers are run, and a downgrade while containers are still running will end in tears. If you’re only running Discourse on your server, you can just stop and delete the container with `docker rm -f app` (your data is safe, and won’t be deleted by this command). If you’re running other containers on the machine as well, you’ll have to figure out what to do.

2. **Downgrade Docker**. Via the magic of the package manager, `apt-get install docker-ce=17.10.0~ce-0~ubuntu` will do the trick. You’ll have to say `y` to the installation, because it’s a downgrade.

3. (optional) **Make sure Docker doesn’t get automatically upgraded again**. That’d really ruin your day, because not only would you have a buggy Docker behind the wheel again, but due to the aforementioned changes in how containers are run, an automated upgrade would likely leave your containers in a kind of limbo state. Not cool.

---

_[View the full topic](https://meta.discourse.org/t/discourse-web-interface-becomes-unresponsive-a-few-minutes-after-starting/76643)._