# High rebuild memory requirements: April 2025 edition **URL:** \ **Category:** Self-hosting\ **Tags:** hosting\ **Created:** [March 31, 2025, 12:37am UTC](https://meta.discourse.org/t/high-rebuild-memory-requirements-april-2025-edition/360419 "2025-03-31T00:37:29Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\ **Post date:** [April 1, 2025, 3:03am UTC](https://meta.discourse.org/t/high-rebuild-memory-requirements-april-2025-edition/360419/3 "2025-04-01T03:03:47Z")
@david has been investigating, we do confirm that as it stands 2gb is enough for docker rebuilds, but not enough for the web upgrader to work. One idea I have tossed around is just shutting down all ruby processes during the web upgrader to save an extra 300-500mb which would leave enough for asset precompilation. A long term approach we are likely going to need to go down for self hosters is [shipping bootstrapped containers](https://meta.discourse.org/t/can-discourse-ship-frequent-docker-images-that-do-not-need-to-be-bootstrapped/33205) which is a pandoras box cause how would a web upgrader be able to pull that one off. We don’t want to mount docker sockets … it sure is a pickle. --- _[View the full topic](https://meta.discourse.org/t/high-rebuild-memory-requirements-april-2025-edition/360419)._