I have error when try to upgrade/rebuild my discourse: FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle install --jobs $(nproc --ignore=1) --retry 3' failed with return # Location of failure: /usr/local/lib/ruby/gems/3.4.0/gems/pups-1.4.0/lib/pups/exec_command.rb:138:in 'Pups::ExecCommand#spawn' exec failed with the params {"cd" => "$home", "tag" => "build", "hook" => "bundle_exec", "cmd" => ["su discourse -c 'bundle install --jobs $(nproc --ignore=1) --retry 3'", "su discourse -c 'bundle clean'", "su discourse -c 'find /var/www/discourse/vendor/bundle -name cache -not -path \"*/gems/*\" -type d -exec rm -rf {} +'", "su discourse -c 'find /var/www/discourse/vendor/bundle -name tmp -type d -exec rm -rf {} +'"]} bootstrap failed with exit code 18 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. I see this above: Fetching gem metadata from https://rubygems.org/. Fetching bundler 4.0.23 Installing bundler 4.0.23 Your Ruby version is 3.4.10, but your Gemfile specified ~> 4.0.0 128:signal-handler (1794492346) Received SIGTERM scheduling shutdown... I have an error when run `sudo git pull` sudo git pull fatal: Out of memory, malloc failed (tried to allocate 104857600000 bytes) fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.

I fixed my git, and it is ok now.

I don’t know, but did you were out of memory?

My memory is normal. I think this is something from docker-image/git memory limit. 100Gb is like git-error memory?

[תמונה] cmdntd: 104857600000 Yeah. That’s 100GB. So something is definitely wrong. So it looks like you have an old /var/discourse–it should do a pull automatically if you do a ./launcher rebuild. Why a git pull wants 100GB I can’t explain.

Is this a standard install? What version is the installation at according to a view-source, or the dashboard? What does this bit of your *.yml file look like? ## Which Git revision should this container use? (default: tests-passed) #version: tests-passed Please post much more of your log file: the last several hundred lines should be enough.

Could I fix `Ruby version` simply?

git --version git version 2.53.0 git remote -v origin https://github.com/discourse/discourse_docker.git (fetch) origin https://github.com/discourse/discourse_docker.git (push)

Thanks. Is this the recipe you’re following: cd /var/discourse git pull ./launcher rebuild app ?

yes, git pull → something wrong in memory ./launcher rebuild app → something wrong in ruby version

Thanks. As I understand it, any ruby version mismatch is not about your OS but about the docker image. Of course the docker image should be internally consistent. The memory issue which causes git pull to fail is important to fix first, but I don’t have any ideas. Just possibly it’s worth trying git fetch --depth=1 to see if that can work. I think it’s always worth checking machine config: df -h / free Also, maybe [תמונה]Facing issue while setting up discourse on my aws ec2 instance ubuntu20, ebs 30gb ram 1gb It’s a good idea also to look in the kernel logs for out of memory conditions dmesg | egrep -i "memory|oom" and if you find any please post the surrounding context dmesg | egrep -i9 "memory|oom"

I have error when try to upgrade/rebuild my discourse

תמיכה

cmdntd (cmdntd) 12 בנובמבר,‏ 2026,‏ 4:50pm 6

It is a standard (alone)

I think it uses default:

  ## Which Git revision should this container use? (default: tests-passed)
  #version: v2.9.0.beta6
  #version: tests-passed

נושא		תגובות	צפיות
First installation - Error on rebuild app Self-hosting	8	530	15 בפברואר,‏ 2024
FAILED Error after update Self-hosting	2	1746	2 ביוני,‏ 2017
HELP: Discourse Update broke app -- fails to rebuild Self-hosting	14	2235	10 בינואר,‏ 2023
Error upgrading Self-hosting	12	1805	20 באוקטובר,‏ 2016
Error while updating through launcher rebuild Self-hosting	2	684	16 באפריל,‏ 2024

I have error when try to upgrade/rebuild my discourse

נושאים קשורים