# Upgrade failing with FAILED TO BOOTSTRAP

**URL:** https://meta.discourse.org/t/upgrade-failing-with-failed-to-bootstrap/218723
**Category:** Self-hosting
**Created:** [February 18, 2022, 7:49pm UTC](https://meta.discourse.org/t/upgrade-failing-with-failed-to-bootstrap/218723 "2022-02-18T19:49:10Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [February 18, 2022, 8:42pm UTC](https://meta.discourse.org/t/upgrade-failing-with-failed-to-bootstrap/218723/5 "2022-02-18T20:42:54Z")

</div>

> [@burke](#):
>
> I’ll try reverting to an even earlier version of docker\_discourse

That won’t work, as the check comes from the main repo. Leaving the data constainers without updates for multiple years is not great, as we shipped performance and security fixes many times on that period.

Yet another reason I do not recomment the separate containers setup.

---

_[View the full topic](https://meta.discourse.org/t/upgrade-failing-with-failed-to-bootstrap/218723)._