Hello, I am running as root and trying to install via docker by the instructions at https://github.com/discourse/discourse/blob/master/docs/INSTALL-digital-ocean.md I am getting this error. This includes the error and some of the log before the error & mkdir -p plugins I, [2015-02-11T17:08:33.012…

This looks like a transient error because https://rubygems.org/ wasn’t responding in time; is your server behind a firewall that might block access to the RubyGems site?

Are there other things that can cause this?

Probably. The logged <Process::Status: pid 329 exit 137> indicates that bundler was killed with a KILL signal which, under normal circumstances, only happens when issued manually with kill -9, during system shutdown if the process didn’t respond to a TERM signal first, or if the kernel has run out…

Hrm, that RAM thing could be an issue, im running on 1.75 gb of RAM, but I have an apache server, phpmyadmin and mysql running on the vps already. Could that be the issue?

I’d say so. Even if the bootstrapping succeeds, it’ll be hard to get Discourse to run; and if you can get it to run, you’ll most likely not enjoy the performance… 1 GB + 1 GB swap is the minimum requirement for the default Discourse setup with nothing else running on the system.

Install terminates while fetching source index from rubygems.org

Product Support Self-hosting

robocoder99 (Robocoder99) February 11, 2015, 10:56pm 3

Highly doubt it. I will try again later, is there anything I can do if the site is blocked?

Topic		Replies	Views
Error while trying to install Discourse Self-hosting	7	1851	December 26, 2017
Rebuild Failed, please help! Self-hosting	7	1164	September 28, 2022
Server in China can't reach rubygems.org so install fails Self-hosting	17	2699	February 10, 2016
Gem::RemoteFetcher::FetchError error during install Self-hosting	3	1795	May 22, 2016
Failing to update an older installation Self-hosting	3	522	September 28, 2023

Install terminates while fetching source index from rubygems.org

Related topics