I’m trying to update a very old installation. I started with this: cd /var/discourse sudo git pull sudo ./launcher rebuild app Then I get a failed and scrolling up the log file the only error is this ERROR: Error installing bundler: bundler-2.5.3 requires Ruby version >= 3.0.0. The current ruby version is 2.7.2.137. How do I go get a new install of Ruby? The system was installed originally from a docker image on Digital Ocean and hasn’t been upgraded much if at all for several years. It’s running on Ubuntu 18.04 I ran ./discourse-doctor and there was a detached head state and then rebuild and then the same Ruby error I’m totally lost now. Any help on how to get an upgrade to work from an ancient version?

Your container image might be pinned to a very old Discourse base image. Can you post your (redacted) container config here?

I don’t know how to do that but from the discourse doctor output I found this DOCKER VERSION: Docker version 19.03.1, build 74b1e89 And it was created 3 years ago

[image] Oogie McGuire: And it was created 3 years ago Given the age of the host machine, your best bet here is probably to take a backup of the site, create a new server, do the install, then restore the backup onto the new server. It’s going to be less work (and a lot easier) than upgrading the existing server.

[image] Michael Brown: your best bet here is probably to take a backup of the site But since the install failed I can’t get discourse running to get a backup. I can and have taken a snapshot of the digital ocean droplet but that’s not really a backup as far as I understand it.

You should be able to just do ./launcher start app to reboot into the old site.

[image] Firepup Sixfifty: ./launcher start app Tried that now getting 502 bad gateway issue :sigh:

OK I’m so far out of my depth here that my solution is to go post a paid for help wanted ad in the Marketplace :grinning:

If you have a snapshot of the droplet with all your data prior to trying to update the container, you should be able to grab a backup from that. If not, you’re almost definitely still fine, but you need someone savvy with the process to be able to pull the data out of it if you can’t get the container back up and running. Right now, even with the bad gateway, if you can get into the container you should be able to run a discourse backup and get your data.

Upgrading very old Discourse Get Ruby error

Product Support Self-hosting

pfaffman (Jay Pfaffman) February 14, 2024, 9:16pm 8

I’d rsync the old /var/discourse to the new server. Or maybe just containers and shared.

Topic		Replies	Views
Can't get Ruby to update so ./launcher rebuild app keeps failing Self-hosting	15	913	May 22, 2024
Discourse Upgrade Failed With Ruby 2.4 or above required Self-hosting	4	1134	July 20, 2018
Old installation failing upgrade Self-hosting unsupported-install	7	349	October 2, 2024
Failed upgrade from 2.9.0.beta14 to 3.1.0.beta Self-hosting	10	1374	January 25, 2023
Failed to upgrade 3.1.0 Beta7 to 3.2.0 Beta3 as of 12/31/2023 Self-hosting	4	607	January 1, 2024

Upgrading very old Discourse Get Ruby error

Related topics