[bitnami/discourse] Error on fresh install with docker compose - relation "translation_overrides" does not exist at character 523

[Bidikay]

Name and Version

bitnami/discourse:3.3.3

What architecture are you using?

amd64

What steps will reproduce the bug?

Fresh install with the docker compose file, adapted for use with Traefik (similar to the link below).

• Docker compose file: https://github.com/bitnami/containers/blob/main/bitnami/discourse/docker-compose.yml
• Docker compose file adapted for Traefik, similar to mine: https://goneuland.de/discourse-mit-docker-compose-und-traefik-installieren

What is the expected behavior?

Proper database population, install script termination and access to discourse on the URL.

What do you see instead?

The pgsql database is not properly populated and throws an error: relation "translation_overrides" does not exist at character 523.
The main container is not able to pursue and the webpage is never displayed on the URL.

The postgresql container log:

postgresql 15:09:09.60 INFO  ==> 
postgresql 15:09:09.61 INFO  ==> Welcome to the Bitnami postgresql container
postgresql 15:09:09.61 INFO  ==> Subscribe to project updates by watching https://github.com/bitnami/containers
postgresql 15:09:09.61 INFO  ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
postgresql 15:09:09.61 INFO  ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise
postgresql 15:09:09.61 INFO  ==> 
postgresql 15:09:09.62 INFO  ==> ** Starting PostgreSQL setup **
postgresql 15:09:09.64 INFO  ==> Validating settings in POSTGRESQL_* env vars..
postgresql 15:09:09.64 INFO  ==> Loading custom pre-init scripts...
postgresql 15:09:09.73 INFO  ==> Initializing PostgreSQL database...
postgresql 15:09:09.77 INFO  ==> pg_hba.conf file not detected. Generating it...
postgresql 15:09:09.78 INFO  ==> Generating local authentication configuration
postgresql 15:09:15.59 INFO  ==> Starting PostgreSQL in background...
postgresql 15:09:17.02 INFO  ==> Creating user bn_discourse
postgresql 15:09:17.04 INFO  ==> Granting access to "bn_discourse" to the database "bitnami_discourse"
postgresql 15:09:17.11 INFO  ==> Setting ownership for the 'public' schema database "bitnami_discourse" to "bn_discourse"
postgresql 15:09:17.24 INFO  ==> Configuring replication parameters
postgresql 15:09:17.33 INFO  ==> Configuring synchronous_replication
postgresql 15:09:17.34 INFO  ==> Configuring fsync
postgresql 15:09:17.41 INFO  ==> Stopping PostgreSQL...
waiting for server to shut down.... done
server stopped
postgresql 15:09:18.43 INFO  ==> Loading custom scripts...
postgresql 15:09:18.43 INFO  ==> Enabling remote connections
postgresql 15:09:18.45 INFO  ==> ** PostgreSQL setup finished! **
postgresql 15:09:18.47 INFO  ==> ** Starting PostgreSQL **
2025-02-05 15:09:18.537 GMT [1] LOG:  pgaudit extension initialized
2025-02-05 15:09:18.623 GMT [1] LOG:  starting PostgreSQL 15.10 on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-02-05 15:09:18.623 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-02-05 15:09:18.623 GMT [1] LOG:  listening on IPv6 address "::", port 5432
2025-02-05 15:09:18.725 GMT [1] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
2025-02-05 15:09:18.846 GMT [143] LOG:  database system was shut down at 2025-02-05 15:09:18 GMT
2025-02-05 15:09:18.987 GMT [1] LOG:  database system is ready to accept connections
2025-02-05 15:09:24.703 GMT [149] ERROR:  relation "translation_overrides" does not exist at character 523
2025-02-05 15:09:24.703 GMT [149] STATEMENT:  SELECT a.attname, format_type(a.atttypid, a.atttypmod),
	       pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod,
	       c.collname, col_description(a.attrelid, a.attnum) AS comment,
	       attidentity AS identity,
	       attgenerated as attgenerated
	  FROM pg_attribute a
	  LEFT JOIN pg_attrdef d ON a.attrelid = d.adrelid AND a.attnum = d.adnum
	  LEFT JOIN pg_type t ON a.atttypid = t.oid
	  LEFT JOIN pg_collation c ON a.attcollation = c.oid AND a.attcollation <> t.typcollation
	 WHERE a.attrelid = '"translation_overrides"'::regclass
	   AND a.attnum > 0 AND NOT a.attisdropped
	 ORDER BY a.attnum

After that, it loops on this error:

> 2025-02-05 15:09:31.855 GMT [151] ERROR:  relation "translation_overrides" does not exist at character 523
2025-02-05 15:09:31.855 GMT [151] STATEMENT:  SELECT a.attname, format_type(a.atttypid, a.atttypmod),
	       pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod,
	       c.collname, col_description(a.attrelid, a.attnum) AS comment,
	       attidentity AS identity,
	       attgenerated as attgenerated
	  FROM pg_attribute a
	  LEFT JOIN pg_attrdef d ON a.attrelid = d.adrelid AND a.attnum = d.adnum
	  LEFT JOIN pg_type t ON a.atttypid = t.oid
	  LEFT JOIN pg_collation c ON a.attcollation = c.oid AND a.attcollation <> t.typcollation
	 WHERE a.attrelid = '"translation_overrides"'::regclass
	   AND a.attnum > 0 AND NOT a.attisdropped
	 ORDER BY a.attnum

Additional information

I tried different versions (tags) of discourse and postgresql containers with the same result.
I also tried to play with user permissions with the same result.

[carrodher]

Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.

If you think that's not the case and would like to contribute a solution, we'd like to invite you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Please don't hesitate to contact us if you have any questions or need help.

Suppose you have questions about the application, customizing its content, or using technology and infrastructure. In that case, we strongly recommend that you consult the forums and user guides provided by the project responsible for the application or technology.

With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.

[pat-s]

Seems to be an issue on the discourse side. It works when you start with 3.1.3 + PG 17.

EDIT: When migrating then to 3.2+, the container aborts after 15s without a proper error logged :/ Yet at least the DB init issues don't appear with 3.1.

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.