I’d like to install Discourse on our Kubernetes cluster. Kubernetes does not use the docker command to deploy images, so I’d need to build a Discourse image locally, push it to our private Docker registry, and then have Kubernetes pull the image from there. This is how we deploy other Docker-based…

There are a bunch of tricks, you can always specify a custom base image in you yaml file eg: Eg: message_bus/examples/chat/docker_container/chat.yml at main · discourse/message_bus · GitHub But you should not really need to do that, for upgrades simply bootstrap a new image and push that our, you …

Okay, I think I’m missing something about how the launcher script (or pups) works here. I have one YAML file for each instance, which looks like this: discourse@hawthorn:~/discourse$ cat containers/clicsargent.yml templates: - "templates/torchbox-web.template.yml" - "private/clicsargent.templ…

Sounds like a pups bug / problem, so that’s where you’ll want to focus your debug efforts.

Yeah @tgxworld mentioned this to me in the past… it is a launcher bug, it does not do 2 levels of inheritance, only 1. I want to get it fixed, maybe try to patch that bash file up to support it

Have you considered using Docker Hub ? It seems with that container you can just supply env vars and it’s not required to run a launcher or your own images… I think… :slight_smile: How amazing would a Kubernetes Helm Chart, or even an Operator for Discourse be… :open_mouth:

Sure, please see [image] Can Discourse ship frequent Docker images that do not need to be bootstrapped? dev There is this open issue (which I just closed) on Discourse Docker repo asking Discourse should behave like a standard docker image a docker user excepts to be a…

Tried bitnami/discourse:latest (1.8.3-dirty as of date) and having a few issues with sidekiq https://github.com/bitnami/bitnami-docker-discourse/issues/25 And there’s probably no way for me to fix it myself as bitnami’s packaging is all a black-box.

I bootstrap with the following in containers/app.yml: templates: - "templates/web.template.yml" - "templates/redis.template.yml" env: LANG: en_US.UTF-8 DISCOURSE_HOSTNAME: 'discourse.mysite.org' DISCOURSE_DB_USERNAME: discourseuser DISCOURSE_DB_NAME: discourse DISCOURSE_DEVELOPER_EMA…

We usually use NGINX+Unicorn as our minimal deployment unit and boot to runit. This should run find with minimal hacking. I there a reason why you are trying to decompose this further? Also I would definitely decompose redis in this kind of setup. Mixing it with the app makes it very hard to scale. …

Hi Sam, Thanks for replying. No, I have no particular reason to decompose, except that Kubernetes expects the entrypoint process to not exit and monitors that process and if it dies it restarts the container. Ideally I would like to run supervisord to spawn and monitor the main processes. So you’r…

Installing on Kubernetes

Support Self-hosting

sam (Sam Saffron) March 4, 2017, 11:53pm 9

Sure, please see

There are a lot of details there.

Topic		Replies	Views
Can Discourse ship frequent Docker images that do not need to be bootstrapped? Development	212	38327	July 13, 2025
Discourse setup on kubernetes cluster using HELM Self-hosting unsupported-install	3	3778	March 3, 2023
Community supported official docker image Development	35	8661	July 22, 2022
Using a launcher built docker image in docker-compose Development	30	7919	September 27, 2024
Unable to create web_only image for a fresh install Self-hosting two-container	10	870	February 25, 2021

Installing on Kubernetes

Related topics