After some days of using ./launcher bootstrap web_only && ./launcher destroy web_only && ./launcher start web_only without issue I ran into issues after trying to use the rails console to set SiteSetting.can_permanently_delete = true using ./launcher enter web_only then rails c Question: Is the rails console accessed differently in separate container mode? After failing to get a successful rebuild and bootstrap I rolled the server back a couple of days prior to implementing AI stuff. No joy! The bootstrap method fails with: FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle install --jobs $(($(nproc) - 1)) --retry 3' failed with return # Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.4.0/lib/pups/exec_command.rb:138:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --jobs $(($(nproc) - 1)) --retry 3'", "su discourse -c 'bundle clean'", "su discourse -c 'find /var/www/discourse/vendor/bundle -name cache -not -path \"*/gems/*\" -type d -exec rm -rf {} +'", "su discourse -c 'find /var/www/discourse/vendor/bundle -name tmp -type d -exec rm -rf {} +'"]} bootstrap failed with exit code 18 ** 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. aee0f5c110bf8ce78f05c138a78712b4a0116fe6662c998b2f29800715036091 ./launcher rebuild web_only errors as well docker: Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint web_only (06b7b1f7f6b476adac20a11a55de776d7350e837407a6c7a6ba582c917f6dd73): Bind for 0.0.0.0:80 After updating Docker Manager from Admin I get You are running an old version of the Discourse image Updates via the web UI are disabled until you run the latest image. To do so log in to your server using SSH and run: cd /var/discourse ./launcher rebuild app Question: You guys have any ideas on what is going on? Here’s the error that causes the build to fail: [2026-02-17T16:51:13.376629 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle install --jobs $(($(nproc) - 1)) --retry 3' Your Ruby version is 3.3.8, but your Gemfile specified ~> 3.4

[image]Move from standalone container to separate web and data containers ./launcher bootstrap data && ./launcher destroy data && ./launcher start data Yeah. That won’t work. It has never worked. I don’t know how someone suggested that it would. I don’t know how I didn’t notice that someone suggested that it would. And the point of the two-container setup, is that you mostly never upgrade data. If you need to upgrade data, then you need to shutdown web only and then rebuild data, then web_only. I updated the OP. If you get port conflict errors then it’s likely because when docker restarted it first restarted the old app container and it’s what is grabbing the port. You can check with docker ps and see if app is running. You hope that it is, as that will explain the port issue. You probably need to docker stop app; docker rm app

You need to scroll up to find the error.

Yes, I have done that but never see anything helpful. Here is latest. exitcode18.txt (43.5 KB)

Here’s the error: [2026-02-17T16:51:13.376629 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle install --jobs $(($(nproc) - 1)) --retry 3' Your Ruby version is 3.3.8, but your Gemfile specified ~> 3.4 Do you have discourse Docker pinned to an old version? Or, it could be a bug, but it seems in) unlikely that such a bug would pass the build test.

Thanks Jay. I saw that but odd messages are not that uncommon with successful builds. [image] pfaffman: Do you have discourse Docker pinned to an old version? No, followed the OP as mentioned. [image] Move from standalone container to separate web and data containers Sysadmins ./launcher bootstrap data && ./launcher destroy data && ./launcher start data fails with error unless first stopping the data container with ./launcher stop data This occurs on instances created fresh with ./discourse-setup --two-container and converted using the longer method. In both cases ./launcher stop web_only && ./launcher rebuild data && ./launcher rebuild web_only and ./launcher bootstrap web_only && ./launcher destroy web_only && ./launcher start web_only work as expected. Am I…

Can you pull /var/discourse? The rebuild should be done using base image 2.0.20260209-1300

Thanks for jumping in @supermathie 2.0.20260209-1300 is used from fresh ./launcher rebuild web_only Status: Downloaded newer image for discourse/base:2.0.20260209-1300 docker.io/discourse/base:2.0.20260209-1300 Ensuring launcher is up to date Launcher is up-to-date Stopping old container + /usr/bin/docker stop -t 600 web_only web_only 2.0.20260209-1300: Pulling from discourse/base Digest: sha256:50d2dae489a9c9916c3d50d880f7f1282fcbe179339b60a8947ab135c1f1f9bf Status: Image is up to date for discourse/base:2.0.20260209-1300 docker.io/discourse/base:2.0.20260209-1300 end of build docker: Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint web_only (9e391a36bdc1a80a6b993a466ffdba25337ce70f1fe74f2b5d8aaca75585322b): Bind for 0.0.0.0:80 failed: port is already allocated failed to set up container networking.txt (74.3 KB) Edit I am thinking the original sin started with the conversion to two containers. [image]Move from standalone container to separate web and data containers ./launcher bootstrap data && ./launcher destroy data && ./launcher start data fails with error unless first stopping the data container with ./launcher stop data This occurs on instances created fresh with ./discourse-setup --two-container and converted using the longer method.

[image] philh: Bind for 0.0.0.0:80 failed: port is already allocated something on your server is already using port 80 and needs to be stopped

[image] philh: am thinking the original sin started with the conversion to two containers. But you said that it had been working and you’d done several rebuilds.

[image] supermathie: something on your server is already using port 80 and needs to be stopped Discourse is the only thing on the server [image] pfaffman: But you said that it had been working and you’d done several rebuilds. I did and do :grinning_face: There are three rebuild options in the original post. The one I reference has never worked .i.e. caused failure [image]Move from standalone container to separate web and data containers ./launcher bootstrap data && ./launcher destroy data && ./launcher start data fails with error unless first stopping the data container with ./launcher stop data This occurs on instances created fresh with ./discourse-setup --two-container and converted using the longer method. In both cases ./launcher stop web_only && ./launcher rebuild data && ./launcher rebuild web_only and ./launcher bootstrap web_only && ./launcher destroy web_only && ./launcher start web_only work as expected.

Build fails due to ruby version mismatch

Product Support Self-hosting

pfaffman (Jay Pfaffman) February 17, 2026, 10:47pm 16

You were just lucky, or more likely, docker hadn’t restarted, and it for some reason (an upgrade or machine reboot).

The ruby version error is a mystery to me.

Topic		Replies	Views
Can't get Ruby to update so ./launcher rebuild app keeps failing Self-hosting	15	916	May 22, 2024
Rebuild failed due to ruby gem incompatibility Self-hosting	8	1877	April 6, 2023
Rebuild failed - FAILED TO BOOTSTRAP Self-hosting	20	2351	December 28, 2023
Updating failed, unable to rebuild Self-hosting	3	1331	June 9, 2021
Failing to update through command line Self-hosting	8	2668	November 12, 2018

Build fails due to ruby version mismatch

Related topics