Ok, next test completed.
I built with the following plugins:
https://github.com/discourse/docker_manager.git
https://github.com/discourse/discourse-data-explorer
https://github.com/communiteq/discourse-legal-compliance
https://github.com/pfaffman/discourse-allow-pm-to-staff
https://github.com/singerscreations/discourse-stopforumspam
https://github.com/discourse/discourse-cakeday
Swap was disabled, so only 4GiB/3.8GB RAM.
Maximum memory usage during build was 3.4GB. Build time was 6m 48s.
Onderweg is het probleem de swapfile, nadat ik deze van 0 naar 2GB heb vergroot, is alles voorlopig in orde.
sudo fallocate -l 2G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab
in de terminal van uw server. Daarna opnieuw opbouwen.
Iām hitting a big increase in memory needed to rebuild. I have 8GB memory and even adding an 8GB swapfile it runs out of space on this step: cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate
Itās a multisite install with four forums. I havenāt had to add a swapfile before.
edit Now tried with 16G swap and itās still running out of memory.
This is under Linux, with minimal plugins enabled. The kernel is killing the process.
Hmmā¦ I wonder, should the docs be updated to reflect higher memory requirements? Did Introducing pre-compiled JS assets for self-hosters help to decrease load? I wold have thought with that change, less RAM is needed 
.
It might have been a few months since I did a rebuild but it was fine before with 8GB ram and no swap. I still havenāt solved this and so all four sites are down.
I donāt know if this is related but it wouldnāt build until I set the environment variable HOME: /var/www/discourse - it would try to write to /root otherwise and get permission denied.
Hmm, Iām seeing over a hundred of these processes:
node /usr/bin/pnpm add pnpm@10.28.0 --loglevel=error --allow-build=@pnpm/exe --no-dangerously-allow-all-builds --config.node-linker=hoisted --config.bin=bin
Is it some kind of fork bomb?
Definitely add a LOT of swap even if itās just to get you back up and running. The advantage of using swap here is builds are a temporary spike.
I use the two container setup and memory is even more under pressure during bootstrap as you also have two running containers. 
I have added 40GB swap now and itās not enough.
Iām seeing hundreds of these node processes, that seems to be the problem?
Iām starting to think the root cause is the same as my earlier issue where I had to HOME: /var/www/discourse otherwise it would try to write files under /root. Iām not sure what to do about it though.
Ok something is very wrong. I would also consider backing up and recreating from scratch.
How would I go about that?
See:
Thanks, I think Iāll revert the whole server to a last-known-good state first and back up from a working system.
Does anyone have ideas about what could have gone wrong?
The problem was indeed do with HOME not being correctly set, adding -H to the sudo command for the multisite migrate fixed it, as detailed here:
https://meta.discourse.org/t/multisite-configuration-with-docker/14084/184?u=yaxu