Bitnami docker image to host discourse

Peter · July 15, 2024, 9:35am

Is it possible using bitnami docker image to hosting discourse on koyeb?

David · July 15, 2024, 11:30am

Hi, yes it is.

You would need to also create PostgreSQL database and a Redis database that you can use for this docker image.

We propose to create serverless PostgreSQL databases and you can leverage other providers to create a serverless Redis database.

Then you would need to configure your image with environment variables as described here: https://hub.docker.com/r/bitnami/discourse

Peter · July 15, 2024, 12:55pm

Hello,I try to delopy it but I got error how to fix it

Welcome to the Bitnami discourse container
discourse 12:50:34.34 INFO  ==> Subscribe to project updates by watching https://github.com/bitnami/containers
discourse 12:50:34.34 INFO  ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
discourse 12:50:34.34 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
discourse 12:50:34.34 INFO  ==> 
discourse 12:50:34.35 INFO  ==> Validating settings in POSTGRESQL_CLIENT_* env vars
discourse 12:50:34.42 WARN  ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
discourse 12:50:34.43 INFO  ==> Creating Discourse configuration file
discourse 12:50:34.46 INFO  ==> Ensuring Discourse directories exist
discourse 12:50:34.47 INFO  ==> Trying to connect to the database server
discourse 12:50:36.15 INFO  ==> Populating database
Application exited with code 1. This usually indicates an application failure. Check that the command used to launch your application is correct.
Instance stopped

David · July 15, 2024, 1:11pm

It is hard to say. It is on the application level. So without additional logs or information, I can’t say why it stopped.

Peter · July 15, 2024, 1:54pm

Hello, I saw a issues on github
And it say

Could you launch the chart with image.debug=true to see if there's more debug information?

How to do it because I try to add it in env but I got :must be a valid environment variable name

David · July 15, 2024, 2:29pm

Did you try the env proposed here?

BITNAMI_DEBUG=true

Peter · July 15, 2024, 3:02pm

Thank you so much for helping me with the inquiry.
It look like redis error

Could it be because I entered the wrong env? I didn’t see the redis user env in the Bitnami README, so I tried using DISCOURSE_REDIS_USER."
This is error code:

07/15/2024, 10:50:29 PM  
stdout  
adaa8378  
----------
07/15/2024, 10:50:29 PM  
stdout  
adaa8378  
        1
07/15/2024, 10:50:29 PM  
stdout  
adaa8378  
(1 row)
07/15/2024, 10:50:29 PM  
stdout  
adaa8378  
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
rake aborted!
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
Redis::ConnectionError: Connection lost (ECONNRESET) (Redis::ConnectionError)
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:306:in `rescue in io'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:298:in `io'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:310:in `read'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:161:in `block in call'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:279:in `block (2 levels) in process'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:411:in `ensure_connected'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:269:in `block in process'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:356:in `logging'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:268:in `process'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:161:in `call'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:139:in `block in connect'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:344:in `with_reconnect'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:114:in `connect'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:409:in `ensure_connected'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:269:in `block in process'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:356:in `logging'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:268:in `process'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:161:in `call'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:270:in `block in send_command'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `synchronize'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `send_command'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/redis-4.8.1/lib/redis/commands/server.rb:90:in `info'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/lib/discourse_redis.rb:42:in `public_send'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/lib/discourse_redis.rb:42:in `block in method_missing'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/lib/discourse_redis.rb:29:in `ignore_readonly'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/lib/discourse_redis.rb:42:in `method_missing'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/config/initializers/001-redis.rb:9:in `<main>'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8/lib/rails/engine.rb:667:in `load'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8/lib/rails/engine.rb:667:in `block in load_config_initializer'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/activesupport-7.0.8/lib/active_support/notifications.rb:208:in `instrument'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8/lib/rails/engine.rb:666:in `load_config_initializer'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8/lib/rails/engine.rb:620:in `block (2 levels) in <class:Engine>'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8/lib/rails/engine.rb:619:in `each'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8/lib/rails/engine.rb:619:in `block in <class:Engine>'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8/lib/rails/initializable.rb:32:in `instance_exec'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8/lib/rails/initializable.rb:32:in `run'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8/lib/rails/initializable.rb:61:in `block in run_initializers'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8/lib/rails/initializable.rb:50:in `each'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8/lib/rails/initializable.rb:50:in `tsort_each_child'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8/lib/rails/initializable.rb:60:in `run_initializers'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8/lib/rails/application.rb:372:in `initialize!'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/config/environment.rb:7:in `<main>'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
<internal:/opt/bitnami/ruby/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
<internal:/opt/bitnami/ruby/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/bootsnap-1.17.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/zeitwerk-2.6.12/lib/zeitwerk/kernel.rb:38:in `require'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8/lib/rails/application.rb:348:in `require_environment!'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8/lib/rails/application.rb:506:in `block in run_tasks_blocks'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/discourse/vendor/bundle/ruby/3.2.0/gems/rake-13.1.0/exe/rake:27:in `<top (required)>'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/ruby/bin/bundle:25:in `load'
07/15/2024, 10:50:34 PM  
stderr  
adaa8378  
/opt/bitnami/ruby/bin/bundle:25:in `<main>'

Topic		Replies	Views
Deployment of multi container app using docker-compose.yaml file Troubleshooting and help help , deployments	10	160	September 4, 2024
Changelog #33 - Logical databases in preview, running containers in privileged mode, and how we built our global deployment engine Announcements docker , regions , postgres , container , global-deployments	1	555	October 26, 2023
Guidance Needed for Integrating Redis on Koyeb How To help , database	3	100	June 17, 2024
Changelog #36 - 1-click apps catalog, per region latencies, connect to your databases, and Docker compose in Koyeb Announcements database , regions , example-applications , services , docker-compose	1	589	November 21, 2023
How to install ffmpeg on koyeb without docker image How To	2	758	August 17, 2023

Bitnami docker image to host discourse

Related topics