Bootstrapping failing for data.yml as well as web_only

I don’t rebuild my containers often and just keep updating from browser based interface.
Today when I wanted ai plugin to be inserted I found that both ‘Data’ and ‘Web_only’ containers/ymls are failing to bootstrap.

Output for discourse doctor is given below

DISCOURSE DOCTOR Tue Feb 27 06:32:10 AM UTC 2024
OS: Linux cpx21-3c-4r-80ssd 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Found containers/web_only.yml

==================== YML SETTINGS ==================== ## # earlier

==================== DOCKER INFO ====================
DOCKER VERSION: Docker version 25.0.3, build 4debf41

DOCKER PROCESSES (docker ps -a)

CONTAINER ID   IMAGE                              COMMAND                  CREATED         STATUS                   PORTS     NAMES
06c70a81e392   local_discourse/web_only           "/sbin/boot"             5 weeks ago     Up 2 weeks                         web_only
6b9837b4be61   discourse/base:2.0.20231218-0429   "/bin/bash -c '/usr/…"   5 weeks ago     Exited (1) 5 weeks ago             elegant_jang
ba6f0dc49ce7   local_discourse/data               "/sbin/boot"             21 months ago   Up 2 weeks                         data

06c70a81e392   local_discourse/web_only   "/sbin/boot"   5 weeks ago     Up 2 weeks             web_only

Discourse container web_only is running

==================== PLUGINS ====================
          - git clone
          - git clone
          - git clone
          - git clone
          - git clone
          - git clone
          - git clone
          - git clone
          - git clone ## for telegram or slack etc chat integrations
#          - git clone
#          - git clone
#          - git clone
#          - git clone
#          - git clone
#          - git clone
#          - git clone
#          - git clone
#gives problem:          - git clone #
#          - git clone #.../learning-management-system-integration-lti-1-3-authentication/196174
#          - git clone #
#          - git clone #
#          - git clone #
#          - git clone #
#          - git clone
#          - git clone ##Discarded in favor of better and later ver Discourse AD Plugin.
#          - git clone
#deprecated          - git clone
#          - git clone #...iscourse-telegram-notifications/60483
#          - git clone #
#          - git clone #
#          - git clone #will be fixed by disco team.
#conflicts with official follow plugin now - git clone # discard if conflicts with non official.
#          - git clone  ## now shifted to a theme component for the same functionality
#          - git clone #
#          - git clone #
#          - git clone #.../pushover-notifications/119258
#          - git clone #
#          - git clone  #Could be a culprit to down wholewebsite
#          - git clone
#          - git clone
#          - git clone
# broken          - git clone #
# broken          - git clone #
# Broken         - git clone #.../reputation-plugin-version-0-2/54758/13
#Integrated in disco core. So no more needed - git clone #...discourse-spoiler-alert/12650

You have what appear to be non-official plugins.
If you are having trouble, you should disable them and try rebuilding again.

See for the official list.

Discourse 3.3.0.beta1
Discourse version at Discourse 3.3.0.beta1
Discourse version at localhost: NOT FOUND
==================== DNS PROBLEM ====================
This server reports NOT FOUND, but reports Discourse 3.3.0.beta1.
This suggests that you have a DNS problem or that an intermediate proxy is to blame.
If you are using Cloudflare, or a CDN, it may be improperly configured.

==================== MEMORY INFORMATION ====================
RAM (MB): 4001

               total        used        free      shared  buff/cache   available
Mem:            3815        1475        1648         113         691        1987
Swap:           2047        1834         213

==================== DISK SPACE CHECK ====================
---------- OS Disk Space ----------
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        75G   39G   34G  54% /

==================== DISK INFORMATION ====================
Disk /dev/sda: 76.3 GiB, 81923145728 bytes, 160006144 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 429800E9-7239-4627-BEC9-7792EEDDB87A

Device      Start       End   Sectors  Size Type
/dev/sda1  528384 160006110 159477727   76G Linux filesystem
/dev/sda14   2048      4095      2048    1M BIOS boot
/dev/sda15   4096    528383    524288  256M EFI System

Partition table entries are not in disk order.

==================== END DISK INFORMATION ====================

==================== MAIL TEST ====================
For a robust test, get an address from
Or just send a test message to yourself.
Email address for mail test? ('n' to skip) []:
Sending mail to . .
Testing sending to using, username:AKIAWRLBIAD2ZJ73AK3F with plain auth.
SMTP server connection successful.
Sending to . .
Mail accepted by SMTP server.

If you do not receive the message, check your SPAM folder
or test again using a service like

If the message is not delivered it is not a problem with Discourse.
Check the SMTP server logs for the above Message ID to see why it
failed to deliver the message.
Replacing: Sending mail to

==================== DONE! ====================

You can examine the output of this script with
LESS=-Ri less /tmp/discourse-debug.txt

BUT FIRST, make sure that you know the first three commands below!!!

Commands to know when viewing the file with the above command (called 'less'):
q              -- quit
/error<ENTER>  -- search for the word 'error'
n              -- search for the next occurrence
g              -- go to the beginning of the file
f              -- go forward a page
b              -- go back a page
G              -- go to the end of the file

As showing above, I’ve disabled almost all plugins with a # sign.
Can anyone pls help as why both containers building is failing?


You definitely need to rebuild the data container to install the AI plugin.

You will need to include the full output from the rebuild for anyone to help know what the problem was.


In addition to rebuilding the ‘data’ container (which needed turning off the web_only container first, for anyone who didn’t know), I was also short on Ram (4gb only, and I had to add 4 gb swap).

Thanks again. Perhaps you’re as important to Discourse (community) as important is this community itself.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.