FYI I just posted a blog post about my Docker adventures: http://samsaffron.com/archive/2013/11/07/discourse-in-a-docker-container

It seems you’re frequently recommending people to use the Docker installer as opposed to following the default Ubuntu Install Guide now. Time for Docker to ascend the throne as Default Install Guide perhaps?

Possibly, we have been running it in production and on multiple sites now for over a month. I only enjoy supporting docker stuff, otherwise there are just too many variables.

A few notable things missing before that can happen Sam’s guide on how to upgrade non-Docker instances to Docker here on meta Blog post on blog.discourse.org blessing Docker as our preferred setup method, explaining why, answering top 5 FAQs about it, and pointing to a newly edited install doc on github that reflects this

What’s the current recommended way to use Docker for Discourse? Readme from GitHub - discourse/discourse_docker: A Docker image for Discourse · GitHub (and using git clone) This is how you would work through it section from Sam’s blog entry http://samsaffron.com/archive/2013/11/07/discourse-in-a-docker-container docker pull samsaffron/discourse

Just as a note, I’ve tried Docker #1 (i.e. Sam’s GitHub readme file) on top of a fresh $5 DigitalOcean VPS (the smallest one). Watching htop: ~80% of the time my CPU is 100% busy with sidekiq, memory usage 450MB out of 490MB. Is this because of Docker or just because of the nature of the environment Discourse is built on? (i.e. ruby, so there is just some minimal requirement that should be always met no matter whether any kind of virtualization is used or not).

[תמונה] sam: That would be a regression we had this week, bootstrap again with latest Sorry, I’m confused - what do you mean? [תמונה] sam: How was the install process? It was easy enough and with no errors. Probably more questions might come later when I try to use it - thanks.

[תמונה] meglio: Sorry, I’m confused - what do you mean? I believe that has to do with this regression: https://meta.discourse.org/t/sidekiq-cpu-load-since-latest-release/9515/22

So if I understand correctly I just have to update my Discourse. But how would I do it with a Docker installation from cli? Please advice. After first bootstrap & run, I couldn’t access via ssh, so I’ve generated an ssh key in the host machine under root and added it to containers/app.yml: ssh_key: ssh-rsa AAAAB3NzaC1… I’ve tried ./launcher stop, bootstrap, start and when I ./launcher ssh app, it still asks for a password: root@0.0.0.0’s password: So I cannot SSH - please advice.

You must destroy the old container to upgrade, see the upgrading discourse instructions in the readme

Discourse in a Docker container

Product Support Self-hosting

sam (Sam Saffron) 11 בינואר,‏ 2014,‏ 3:11am 8

That would be a regression we had this week, bootstrap again with latest

The instructions on guthub are the most up to date

I would avoid any vps with less than a gb of ram

How was the install process?

נושא		תגובות	צפיות
Why does Discourse have to use Docker? Self-hosting docker	34	10980	29 באפריל,‏ 2015
High-CPU / High memory on fresh discourse install Self-hosting server-resources	5	1720	17 באוקטובר,‏ 2018
Failed to install Discourse in Ubuntu14.04: docker problems Self-hosting docker	19	8675	25 בינואר,‏ 2015
Manually update Discourse and Docker image to latest Self-Hosting how-to	13	112329	16 בינואר,‏ 2025
Discourse-docker run with unicorn memory issue Self-hosting server-resources	6	1217	23 בדצמבר,‏ 2019

Discourse in a Docker container

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