# Plotseling mislukt het opstarten

**URL:** https://meta.discourse.org/t/suddenly-boot-strapping-is-failing/250106
**Category:** Self-hosting
**Tags:** two-container
**Created:** [29 december 2022 om 10:32 UTC](https://meta.discourse.org/t/suddenly-boot-strapping-is-failing/250106 "2022-12-29T10:32:21Z")
**Posts on this page:** 1
**Showing post:** 14

<div class="post-metadata">

### Author: ![Bathinda](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bathinda/32/135888_2.png) [@Bathinda](https://meta.discourse.org/u/Bathinda)
#### Post date: [30 december 2022 om 08:00 UTC](https://meta.discourse.org/t/suddenly-boot-strapping-is-failing/250106/14 "2022-12-30T08:00:16Z")

</div>

You’re correct!!

I rebooted my ubuntu server, which allowed me to have around 7 to 800 MBs of free ram on my instance and bootstrapping succeeded. I’d have stop my container before another BS, if another rebuild/bs didn’t succeed after enabling the desired plugins.

But I’m astonished at the new ram demands of the discourse. As the cost of the instance/droplet is almost doubling when I go from 4 to 8gb ram. Which I don’t wish, considering that mine is a very very very small website (perhaps 10 visitors a day). Earlier Discourse’s [standard install](https://meta.discourse.org/t/142537?silent=true) shown to demand only 1 to 2 gb ram.

Thanks very much for helping me recognizing what was going wrong.

---

_[View the full topic](https://meta.discourse.org/t/suddenly-boot-strapping-is-failing/250106)._