I’ve got a rebuild that’s failing, I think due to this. It’s running Ubuntu 16.04 with Docker version 17.05.0-ce, build 89658be, which I know is suspect, but I wanted to give this person one more rebuild if at all possible. I, [2023-12-06T16:10:12.656984 #1] INFO -- : > cd /var/www/discourse && su…

[image] Jay Pfaffman: To see why this extension failed to compile, please check the mkmf.log which can be found here: /var/www/discourse/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/rbtrace-0.5.0/mkmf.log [image] Jay Pfaffman: libraries and/or headers. Check the mkmf.log file …

I think that file is inside the container that’s failing to build, so it’ll be a bit hard to catch, I think. I think I saw someone else with a similar error that went away when they upgraded Docker (they were on a later OS), so I’m going to just think that’s what the problem is. Thanks

[image] Jay Pfaffman: a bit hard to catch Possibly. But on my system there’s a selection of such - might be worth a look, in case they are not just fossils. ls -ltr /var/lib/docker/overlay2/*/*/var/www/discourse/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/rbtrace*/mkmf.log

Well. I’ll be. Look! root@www:~# find /var/lib/docker -name mkmf.log|grep rbtrac|xargs ls -tl -rw-r--r-- 1 1000 1000 35035 Oct 23 19:45 /var/lib/docker/aufs/diff/53a65982150d745a518e8e8b3d1c4e5e21df4aeaf387d952d9018f688e676391/var/www/discourse/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.…

Hmm might be a red herring, as I see the same fails and yet apparently nothing is broken in my case. Maybe these logs are some kind of fossil in the image?

[image] Ed S: Maybe these logs are some kind of fossil in the image? Could be. Anyway, no one else has this problem, so I think I’m not going to worry about it and just tell this person that if they want to upgrade discourse they’ll have to update the vm and OS. Thanks for your help

I just tried a rebuild on a standard docker installation (with Docker from Debian Bullseye, docker.io apt package) and it succeeded, so this at least establishes that self hosted installations are not broken, that is, that launcher rebuild is not reproducibly resulting in failed installations due to…

[image] Leonardo Mosquera: there any chance your clone of discourse_docker failed to git pull before starting the rebuild, and is thus on an old commit That’s a possibility. Recent launcher does a git pull (and it’s been a long time that it started doing to git pull). Maybe I’ll give it one m…

This may help someone as it worked for us without upgrading the Ubuntu 16. Run sudo apt update && sudo apt upgrade command Then run the discourse launcher ./launcher rebuild app The error went away for us.

I tried a fix from a different forum. In the launcher script, I replaced: image="discourse/base:2.0.20231218-0429" with: image="discourse/base:2.0.20231230-0022" This pulls a newer image that contains rbtrace-0.5.1, which makes it work. Got it from here: Discourse Build Error: "An error occurre…

Rebuild failure: "extconf failed, exit code 1" -- due to old Docker?

Support Self-hosting

Topic		Replies	Views
Rebuild failed - FAILED TO BOOTSTRAP Self-hosting	20	2065	December 28, 2023
Discourse Build Error: “An error occurred while installing rbtrace (0.5.1), and Bundler cannot continue Self-hosting	20	2724	January 25, 2024
Failing to update through command line Self-hosting	8	2530	November 12, 2018
3.2.0.beta4 failed to build -- Site down Self-hosting	14	596	January 11, 2024
Update Fails with Unexpected Error During Rebuild Self-hosting	9	1300	December 16, 2023

Rebuild failure: "extconf failed, exit code 1" -- due to old Docker?

Related topics