For the past few weeks or so, I cannot rebuild our Discourse forum software. Each time, we get this Bundler error: "An error occurred while installing rbtrace (0.5.1), and Bundler cannot continue." failing: FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle install --retry 3 --jobs 4' failed with return # Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle config --local deployment true'", "su discourse -c 'bundle config --local without \"development test\"'", "su discourse -c 'bundle install --retry 3 --jobs 4'"]} bootstrap failed with exit code 5 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. ./discourse-doctor may help diagnose the problem. dfd1d73cc65b60ab8b8963ad9bdb005500322808bf8766cf90c07c91d3dea615 so I tried, from this reference gem install rbtrace -v '0.5.1' --source 'http://rubygems.org/' -- --with-cflags=-Wno-implicit-function-declaration with success: Building native extensions with: '--with-cflags=-Wno-implicit-function-declaration' This could take a while... Successfully installed rbtrace-0.5.1 Parsing documentation for rbtrace-0.5.1 Done installing documentation for rbtrace after 0 seconds 1 gem installed But it keeps failing..... An error occurred while installing rbtrace (0.5.1), and Bundler cannot continue. If this error cannot be fixed, I will need to rebuild Discourse from scratch in an entire new directory structure and change all our admin scripts, etc. :frowning:

Hi @vbe, If anyone askes you again, you can advise them that this rbtrace error can be also fixed by editing the discourse launcher script and replacing this line: image="discourse/base:2.0.20231218-0429" to this line (newer version of discourse docker base image). image="discourse/base:2.0.20231230-0022" This is easier than editing the .yml build files; and I have modified our build (launcher script) as above as well; and removed the (advanced) changes to the .yml files. Cheers

[image] Neo: Are they simply that incompetent? Yes. Next question?

[image] hicksd8: Yes. Next question? It's hard to suffer those fools easily! I keep hoping they will just release an update which pulls a newer version of the base image which uses rbtrace 0.5.1; ..... but no .... they are way off target in their (lack of) analysis. This is the file which needs to be updated (launcher) which was committed 3 weeks ago where the base image was released with rbtrace 0.5.0 before the rbtrace v0.5.1 upgrade was released, [Screenshot 2024-01-11 at 7.26.18 PM] This is an easy problem to solve; but they cannot solve it !!! What are they waiting for! haha :frowning:

[image] Neo: What are they waiting for! haha They're waiting for a link to this topic here to be posted over on Meta. That would speed things up (and they'll never speak to us again!!).

One admin seems to have resolved the issue by rebuilding on a new server; but I understand docker images are built from sources (and runtime libs) outside the host by pulling the necessary code. Quote: Docker images contain their own complete set of runtime libraries . They do not (and can not) depend on the host system's libraries. The kernel is shared, which is an occasional source of trouble, but host system libraries shouldn't cause an image to work on one host system Linux distribution but not another." Quick Reference: [image] Depending running containers from host libraries General docker Hello, Maybe someone make clear for me the issue below. Is the containers use the system libraries, packages, etc? How it depend on host system when it started. I have dockerized Drupal with separate containers on one host Ubuntu 14.04.5 LTS: ... Reading time: 1 mins 🕑 Likes: 1 ❤ Anyone have thoughts on this? See Also: [image] docker buildx build

[image] hicksd8: They're waiting for a link to this topic here to be posted over on Meta. That would speed things up (and they'll never speak to us again!!). Few big ego types ever speak to me again when comparing depth of technical abilities (after all, I'm and graybeard and have been doing this for around 50 years, and my analytical skills are quite sharp, IIDSSM) software troubleshooting skills and Discourse has already banned or silenced me twice before for not kissing their ***es, so better not post any link over there. It's not our duty to be a support team for meta discourse customers. We are not going for a beer together anytime soon! :slight_smile:

It's not finished: [image] Rebuild failed installation Hello I’m on this commit in /var/discourse commit fcce1376043adeb09e21ec1ec079a41e4d29fe6e (HEAD -> main, origin/main, origin/HEAD) Author: Chris Rendle-Short Date: Tue Dec 19 10:30:51 2023 +1100 Bump default base image to...

Amazing.... it's been a month since the commit below (18 December 2023) which was released a few days (too) early to give the rbtrace ruby gem the required time to release before the commit below. Can we say, "the commit below jumped the gun" ? That's what we used to say when I was a kid. [Screenshot 2024-01-14 at 7.30.01 PM]

Thank you for the clarification

its easily confusing for folks who are not hands-on Ruby-on-Rails software developers!

Finally! Six months later, Discourse updates the base docker image! DEV: Bump default base image for launcher to `discourse/base:2.0.20240502-0021` (#795) committed 01:46AM - 02 May 24 UTC (UTC) [tgxworld] tgxworld +1 -1 This is necessary to pull in 303b646c3c48fc3179af954433d9fa797e70a3b9

Unix Linux Community

Discourse Build Error: "An error occurred while installing rbtrace (0.5.1), and Bundler cannot continue."

Discourse Discourse System Administration