I really would like to have an official helm chart for discourse with an official docker image. I just opened this issue. I’d like to have the consent of the discourse maintainers to make this happening. Hope you can help make this happen. All you need to do is to give a yes :slight_smile: Thanks!

@sam if discourse agree on having an official docker image, we need: a docker repo under discourse organization (or call it official-docker or as you want) give write right to pierreozoux and docker-library-bot And I’ll take care of the rest. You don’t need to get involved except if you want to. If you want to get even less involved, then just agree on the issue I mentioned. I’ll see with docker to create a repo for the Dockerfile.

Anything official means we 100% own it and are fully responsible for it, so my default answer on these kinds of requests is generally gonna be a hard no.

Can you describe the exact mechanics of what you are proposing here?

You might want to walk before you run. Start by making something unofficial, that works, so everyone can see (a) that it works, and (b) how it works.

[תמונה] codinghorror: Anything official means we 100% own it and are fully responsible for it, so my default answer on these kinds of requests is generally gonna be a hard no. This is an official docker image - official here is an adjective for docker. Think of it as a debian package. In debian, I wouldn’t need your agreement to make a debian package (except if you specifically disagree). In docker, it is a docker policy, I need an agreement from you, it is better. This still doesn’t mean you have to support it. We could still state that the official way of installing it is with the laucher and this is not official discourse thing, just a community effort. [תמונה] sam: Can you describe the exact mechanics of what you are proposing here? Ok, just realized it was the wrong link in the original issue, I pointed to this issue with a bit more background. (will updated the post) [תמונה] mpalmer: You might want to walk before you run. Start by making something unofficial, that works, so everyone can see (a) that it works, and (b) how it works. I’m running this docker-compose since 2 years in production. I host around 5 forums with that, the last one being forum.chatons.org a collective with 58 free software hosters in France. I already created 4 official docker images (rocket.chat, Nextcloud, piwik..). And also did the official helm chart for rocket.chat. As a day job, I work as a consultant to help companies to migrate to kubernetes. During my docker trainings, I actually make people dockerize discourse :stuck_out_tongue: I find it nice as it is a real example! I developed a docker-compose PaaS called libre.sh and we are rebooting the project with kubernetes. I just think that I’ll migrate first the discourses, that’s why I’m here again to discuss about this topic. What makes me want so hard this official image is the talk for the freedom box. I want to push my changes upstream to collaborate. Of course, I can maintain my little docker image on my side, but many people are doing the same, and it is so much valuable engineering time lost.. it makes me sad. I hope I managed to convince you, i still have some arguments in my pocket!

This sounds great! I’m curious, what’s your way around pg major version updates? Our launcher based image handle everything for the end user automatically, but people using an external image will have to deal with it themselves right? Looks the community can’t agree in a way forward: Upgrading between major versions? · Issue #37 · docker-library/postgres · GitHub

[תמונה] Falco: I’m curious, what’s your way around pg major version updates? I never did that (yet - never had to), but I’ll try in the coming weeks, now I’m curious :slight_smile: (and well, this question, is obviously not part of the discourse docker image) [תמונה] Falco: Our launcher based image handle everything for the end user automatically, but people using an external image will have to deal with it themselves right? I really do think you did a great job with this launcher, but we are sys admins, and I think we all love our standardization, and this is not standard. i think it is really perfect for the one that want to quickly get started on a droplet. But yeah, for docker image, people will have to deal with that themself. And we’ll need to put a big warning about that specific.

I’m very excited about this project :smile:. I see that you run sidekiq and unicorn in separate containers, so that mean it will use, at least, double the resources when using this setup. No problem, since this will be only for very advanced setups. Also, assets / migrations run on every boot. And, what do you think about plugin support? Today, we use clone those before the bundle install using a launcher hook.

Some additional questions, How do you handle logging and log rotation considering even a minimal rails install of Discourse with NGINX in a dedicated container would still have, unicorn and production logs.

Community supported official docker image

מפתח

sam (Sam Saffron) 24 במרץ,‏ 2018,‏ 10:09pm 2

Its hard to give a yes when its unclear what exactly is being proposed and how much extra work it introduces us.

נושא		תגובות	צפיות
Is Docker image discourse/discourse considered safe and production-ready? Self-hosting hosting	30	3723	26 במאי,‏ 2026
Can Discourse ship frequent Docker images that do not need to be bootstrapped? Development	211	41868	13 ביולי,‏ 2025
Using a launcher built docker image in docker-compose Development	30	8537	27 בספטמבר,‏ 2024
Installing on Kubernetes Self-hosting unsupported-install	56	26575	9 ביוני,‏ 2026
Container restart - discourse tries to reinstall Self-hosting unsupported-install	22	3353	30 ביולי,‏ 2020

Community supported official docker image

נושאים קשורים