Hi there, I have recently migrated a server image that has Docker Discourse installed on it I can get everything up and running, but I need to re-issue the SSL cert Since the old server had SSL configured, I’m following this guide’s suggestion and running ./launcher rebuild app This then causes docker to pull and update a bunch of things. The current image is Discourse 2.6.0.beta3 - https://github.com/discourse/discourse version 29f7e0689f61c5d85960a88f741ac3abced12d3e The first time I ran it, it gave me the Postgres Upgrade message, so I ran ./launcher rebuild app again as instructed Now it just keeps failing every time, I believe due to this error with an insufficient version of ruby installed ERROR: Error installing bundler: bundler-2.5.3 requires Ruby version >= 3.0.0. The current ruby version is 2.7.2.137. Here is the full output FAILED -------------------- Pups::ExecError: cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock) failed with return # Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,\"\"); print $0 }' Gemfile.lock)", "find $home ! -user discourse -exec chown discourse {} \\+"]} 2ad07f29ace1b5396d9944fc4fc5a1ec712727280e8bb3df760367d08bfe6a25 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. I would have thought Docker would update the Ruby version as needed? I have tried manually logging into the container and install RVM, and activated Ruby v3+ but I still continue to get the same error I’m a bit lost at this stage, and wonder is the version installed just too old to be upgraded with ./launcher? Any advise would be greatly appreciated!

[image] robobobo: Here is the full error FAILED -------------------- Pups::ExecError: cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock) failed with return # Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,\"\"); print $0 }' Gemfile.lock)", "find $home ! -user discourse -exec chown discourse {} \\+"]} 2ad07f29ace1b5396d9944fc4fc5a1ec712727280e8bb3df760367d08bfe6a25 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. Just a note, that is not the error, the actual errors will be further up.

Thanks Jay, I feared that might be the only way forward I guess I just need to find a way and hope I can copy across the database so everything isn’t lost

Try updating all your packages using apt upgrade

It’s not hard. You can just make a backup, or do Move a Discourse site to another VPS with rsync. You have nothing to lose since your existing site stays intact. It’s the safest possible way forward.

I’ve updated absolutely everything I could, including the Ubuntu version of the server and confirmed I have ruby v3.1 running. Problem is I suspect it’s the ruby version needed in the container which is controlled by docker, and I can’t seem to get it to update

I did manage to install a clean version and get it up and running 3.3.0.beta3-dev However, when I restored the backup from the old site, it doesn’t look like it’s restored correctly and now the login page doesn’t work. Looking at the JS console there’s a Discourse is not defined error whenever I click the login/signup buttons. I reckon because of the big difference in versions it’s not a simple recovery of a 2.6.0 backup to a clean 3.3.0 install Moving everything to a new server just isn’t working for me, as I can’t run ./launcher rebuild app without this ruby error blocking me each time.

[image] robobobo: I reckon because of the big difference in versions it’s not a simple recovery of a 2.6.0 backup to a clean 3.3.0 install If you’re running an upgrade that far it’s a good bet that your themes are broken. Try safe-mode.

[image] Using Safe Mode to troubleshoot issues with themes and plugins Site Management bookmark This guide explains how to use Discourse’s Safe Mode to troubleshoot issues with themes and plugins. person_raising_hand Required user level: All users Discourse offers a “JavaScript Safe Mode” that allows any user to isolate the root cause of JavaScript issues caused by plugins, themes, or theme components. This feature is particularly useful for troubleshooting problems on your Discourse site. Accessing Safe Mode To access Safe Mode, follow these steps: Open a new browse…

[image] robobobo: a clean 3.3.0 install Technically there is no 3.3.0 yet, we are still going through the betas.

Can't get Ruby to update so ./launcher rebuild app keeps failing

Product Support Self-hosting

pfaffman (Jay Pfaffman) May 15, 2024, 6:07am 3

I recommend starting with a new image and doing a standard install.

Topic		Replies	Views
Upgrading very old Discourse Get Ruby error Self-hosting	9	689	February 14, 2024
Discourse Upgrade Failed With Ruby 2.4 or above required Self-hosting	4	1134	July 20, 2018
Rebuild failed due to ruby gem incompatibility Self-hosting	8	1877	April 6, 2023
Build fails due to ruby version mismatch Self-hosting	16	619	February 17, 2026
Breaking change for people on stable versions (v3.2.1 and down) with discourse_docker Bug docker , stable	2	535	May 20, 2024

Can't get Ruby to update so ./launcher rebuild app keeps failing

Related topics