Apt-get update fails inside container yarn repo not signed

As I am an ‘ambitious amateur’, a quick question:
How do I execute the Curl command ‘inside the container’?

In a post above I include that the curl command can be included in the template that does the apt-get. Apt-get update fails inside container yarn repo not signed - #6 by rahim123

@fidelio Hi there, do you need to connect to another database like SQLite from within your Discourse instance, i.e. are you performing a data import from another forum? Otherwise you can disable that functionality and the normal Discourse app container will rebuild fine.

My guess is that he’s not upgraded to PG 13 and is using the pg12 template? That’s a problem that should be solved anyway. And it’s a good bet that the os needs to be upgraded and moving to a new vm is what to do.

1 Like

Hi @rahim123 . No i don’t need to do either of those at this stage. How do I disable the functionality?

@pfaffman Ah, it just seemed weird that his error log was complaining about trying to install libsqlite3-dev , or does Discourse normally use that for something?

@fidelio Could you paste here the templates: section of your /var/discourse/containers/app.yml file? Make sure not to include any passwords that are present farther down in the file. You can also run /var/discourse/discourse-doctor and it will help you generate a publicly shareable report of how your system is configured.

1 Like

@rahim123 Sure here is the discourse-doctor report:

Found containers/app.yml

==================== YML SETTINGS ====================

==================== DOCKER INFO ====================
DOCKER VERSION: Docker version 18.06.1-ce, build e68fc7a

DOCKER PROCESSES (docker ps -a)

CONTAINER ID        IMAGE                           COMMAND             CREATED             STATUS              PORTS                                      NAMES
ce58652241d9        local_discourse/app             "/sbin/boot"        2 weeks ago         Up 14 minutes>80/tcp,>443/tcp   app
8e6b8ec432b4        local_discourse/mail-receiver   "/sbin/boot"        11 months ago       Up 11 months>25/tcp                         mail-receiver

ce58652241d9        local_discourse/app             "/sbin/boot"        2 weeks ago         Up 14 minutes>80/tcp,>443/tcp   app

Discourse container app is running

==================== PLUGINS ====================
          - git clone https://github.com/discourse/docker_manager.git
          - git clone  https://github.com/davidtaylorhq/discourse-whos-online.git
          - git clone https://github.com/gdpelican/babble.git
          - git clone https://github.com/angusmcleod/discourse-quick-messages.git
          - git clone https://github.com/angusmcleod/discourse-events.git
          - git clone https://github.com/discourse/discourse-calendar.git
          - git clone https://github.com/discourse/discourse-data-explorer.git
          - git clone https://github.com/davidtaylorhq/discourse-telegram-notifications.git

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

See https://github.com/discourse/discourse/blob/main/lib/plugin/metadata.rb for the official list.

Discourse version at community.bfs-filmeditor.de: TYPO3 CMS
Discourse version at localhost: TYPO3 CMS

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

              total        used        free      shared  buff/cache   available
Mem:           3944        1272        1236        1067        1436        1364
Swap:             0           0           0

==================== DISK SPACE CHECK ====================
---------- OS Disk Space ----------
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda1        78G   60G   18G  78% /

---------- Container Disk Space ----------
Filesystem      Size  Used Avail Use% Mounted on
overlay          78G   60G   18G  78% /
/dev/vda1        78G   60G   18G  78% /shared
/dev/vda1        78G   60G   18G  78% /var/log

==================== DISK INFORMATION ====================
Disk /dev/vda: 80 GiB, 85899345920 bytes, 167772160 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: C1F9A1FE-534C-4DAC-9299-5CC180C29DCE

Device      Start       End   Sectors  Size Type
/dev/vda1  227328 167772126 167544799 79.9G Linux filesystem
/dev/vda14   2048     10239      8192    4M BIOS boot
/dev/vda15  10240    227327    217088  106M Microsoft basic data

Partition table entries are not in disk order.

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

I have disabled quick messages but not yet removed it.

FWIW, I think babble has been broken for some time:


I thought that discourse-doctor showed which templates are enabled, guess not. Could you also please post this?

1 Like

It doesn’t. Though it seems like it might be a good idea, this is the first time that I remember that it was important.

1 Like

Here it is:

 GNU nano 2.9.3                                                                         containers/app.yml                                                                                   

## this is the all-in-one, standalone Discourse Docker container template
## After making changes to this file, you MUST rebuild
## /var/discourse/launcher rebuild app
## visit http://www.yamllint.com/ to validate this file as needed

  - "templates/postgres.template.yml"
  - "templates/redis.template.yml"
  - "templates/web.template.yml"
  - "templates/web.ratelimited.template.yml"
## Uncomment these two lines if you wish to add Lets Encrypt (https)
  - "templates/web.ssl.template.yml"
  - "templates/web.letsencrypt.ssl.template.yml"
  - "templates/import/mbox.template.yml"
## which TCP/IP ports should this container expose?
## If you want Discourse to share a port with another webserver like Apache or nginx,
## see https://meta.discourse.org/t/17247 for details
  - "80:80"   # http
  - "443:443" # https

  db_default_text_search_config: "pg_catalog.english"

  ## Set db_shared_buffers to a max of 25% of the total memory.
  ## will be set automatically by bootstrap based on detected RAM, or you can override
  db_shared_buffers: "1024MB"

  ## can improve sorting performance, but adds memory usage per-connection
  #db_work_mem: "40MB"

  ## Which Git revision should this container use? (default: tests-passed)
  #version: tests-passed

  LANG: en_US.UTF-8

  ## How many concurrent web requests are supported? Depends on memory and CPU cores.
  ## will be set automatically by bootstrap based on detected CPUs, or you can override

This is the problem I think, try putting a # in front of it and doing a ./launcher rebuild app .


That’s what the issue is. Did you do an import from mbox? Is it installed for some other reason?

You can either comment it out or modify that template as I mentioned earlier. If you do, you’ll need to do a git stash before you can upgrade.


Yes, l used mbox when first moving from our mailing list!

Thanks guys, I will clean up my container and try to rebuild.


Good luck, hope you can get it back online soon!


Hey @Falco – is this on the map?

I also was unable to make the postgres templates work because of this bug: Problem with postgres upgrade

1 Like

Yes, I should be able to address it next week.


Did it get into the base image version bump the just got accepted?

Can you also take a look at bash tab completion for launcher + discourse-setup by pfaffman · Pull Request #676 · discourse/discourse_docker · GitHub? I would give to have it on all of the sites I touch.

Fixed 10h ago by @schleifer

Maybe open a topic to discuss and demo that?


This topic was automatically closed after 4 days. New replies are no longer allowed.