I can happily report that discourse_docker works just fine on a CoreOS image. There was exactly one thing I had to modify: localhost discourse # git --no-pager diff diff --git a/launcher b/launcher index bc7f204..07dca0d 100755 --- a/launcher +++ b/launcher @@ -16,7 +16,7 @@ local_discourse=local_d…

Interesting [imagem] Red Hat OpenShift A unified application development platform that lets you build, modernize, and deploy applications at scale on your choice of hybrid cloud infrastructure. claims 40% less memory use automatic full OS update scheme nati…

[imagem] julsevern: This release uses btrfs instead of aufs I liked this topic, but you just made me double like it. aufs is a crutch, startup time of Ruby processes is heavily impacted. device mapper has always been flaky. If you ever wonder why rails c takes so long, or rake assets:precom…

Regarding memory use you should not expect huge across the board gains, the 40% figure is just relating to the “base OS” not the applications running. Discourse consumes the vast majority of memory and mem usage is identical. However, performance wise it is quite interesting. btrfs means that we h…

Ha yes, it cannot reduce memory usage magically :slight_smile: and the OS doesn’t have build and scripting tools whatsoever. The promised 40% is about the default not loaded OS footprint. I had to increase the coreos KVM instance’s memory allocation from 1G, because of OOM errors in Discourse. Howe…

[imagem] sam: we halve our boot time, so booting Discourse goes from 12 seconds down to 6. I suspect this filesystem would also greatly increase upgrade times as well? Since that involves a lot of file magic.

If I were running in a fleet I would run a central registry and just pull from it as needed. Basically you bootstrap somewhere push to central registry. Then pull that image to the fleet and launch it using ./launcher start.

[imagem] codinghorror: I am curious if that 40% less memory figure is true! has anyone compared a 1GB DO Ubuntu image with Discourse, to a 1GB DO CoreOS image? On a 1 GB CoreOS machine without swap, I had to cut down the number of unicorn instances to two. Also the update function (at /admin/…

That’s the same as it is on Ubuntu. We recommend only 2 workers on 1GB per the official install docs, and we also recommend setting up swap to cover the upgrade case – upgrading chews through a ton of memory.

@sam Just saw the comparisons you made between ubuntu and coreos. Do you think its worth switching from ubuntu to CoreOS?

@nahtnam I’d wait until a coreos stable release contains a version of docker which is actually supported by the launcher script.

Report on using discourse_docker on a CoreOS image

Product Support Self-hosting

maze (Martin) Setembro 10, 2014, 7:48am 8

On a 1 GB CoreOS machine without swap, I had to cut down the number of unicorn instances to two. Also the update function (at /admin/upgrade) leads to out-of-memory situations. I have to stop the unicorns before trying to do that.

Tópico		Respostas	Visualizações
Installation Failed on CoreOS? Self-hosting	13	2267	31 de Janeiro de 2018
Discourse in a Docker container Self-hosting hosting	27	13070	3 de Fevereiro de 2014
Can Discourse ship frequent Docker images that do not need to be bootstrapped? Development	211	41324	13 de Julho de 2025
Failed to Bootstrap due to out of memory Self-hosting	4	1481	16 de Setembro de 2016
Why does Discourse have to use Docker? Self-hosting docker	34	10869	29 de Abril de 2015

Report on using discourse_docker on a CoreOS image

Tópicos relacionados