Using a launcher built docker image in docker-compose

dev
1

I’ve been asked to make a docker-compose file for a discourse project I’m working on to make it as simple as possible for developers and sysadmins we’re working with to fire up a discourse instance to test against.

I’ve read through Can Discourse ship frequent Docker images that do not need to be bootstrapped? and came away the notions that ./launcher was really necessary in order to keep the right versions of software in play, to make installation of plugins seamless and deterministic, and to enable software upgrades via the web UI, all ./launcher was doing was working out the correct command line options to send to docker, using docker-compose to build the image did not work given the complexities involved, and interestingly, that I could just use the docker image created by ./launcher and use that with docker-compose.

I rebuilt the app, copied the final command to launch the instance, converted that to a docker-compose.yml file and started the container. I just have the init scripts to go.

I’m thinking I’d have the scripts … the initial init scripts being accessible in the shared folder and getting using docker-compose run or docker exec to get to the bootstrapping.

Has anyone done this?
Are there any guides as to what subset of scripts need to be run is the base image has already been built?

Cheers and thanks

Keith John Hutchison

Background Research.

I’ve read through install-with-docker-compose and it works well enough … main issues is it’s slightly behind the official release, and there is no command line support for discourse and rails.

I’ve since discovered that adding discourse and rails command line support will be trivial as they are bash scripts.

I’ve read through Beginners Guide to Install Discourse for Development using Docker and I got a local instance of docker running on my Mac.

The main issue here was I had to bootstrap the image which is something I’ve been asked to avoid.

I restored locally after running discourse enable_restore from a staging backup and it looks good.

I’ve investigated bitnami/discourse. It worked … main issues was it was a fair bit behind the official image, quite a bit different with paths and it was slower than Install with Docker compose

2

Yes.

No. The only supported way to run discourse is through launcher. If you do it at other way, you’re on your own. If you use bitnami you will need to get support from them, and I’m pretty sure they provide none

If you have a budget, I might be able to help. My contact info is in my profile.

3

G’day Jay

I wasn’t asking for help with Bitnami … that was just background. It would be too different from the staging environments that uses .launcher.

I’m following the lead from Can Discourse ship frequent Docker images that do not need to be bootstrapped? which basically said using the output from .launcher is the way to go if you want to use docker-composer.

1 Like
4

But is it simple if said image ends up not being representative, lags behind official releases and said developers and sysadmins are unable to get support here?

It’s always frustrating for users when tell them their install is completely unsupported, you’re effectively asking for guidance in building another unsupportable install. Do the IndieHosters understand that you/they will be totally on their own with this?

1 Like
5

I totally agree. That’s why I suggested to our dev lead not to use the bitnami/discourse images, why he asked me to research the best way forward and why I’ve chosen to use the image(s) created by ./launcher as suggested by

So the question for me now is, how to generate the base image(s) using launcher and bring up the environment using compose?

I’ve already tried using the image created by ./launcher rebuild app.
I’m about to look at ./launcher bootstrap app.

6

… bootstrap is called by rebuild so there would be no difference in the resultant image …

7

The image from bootstrap is fine, in fact it is running here on meta, PG is running on AWS RDS, Redis in a dedicated container.

3 Likes
8

I know the image is fine Sam. We’re using it on a staging server. I clearly understand that what is lacking here currently is my knowledge on how to run the scripts required to setup the shared folders within docker-compose.

9

I am super confused at why you would even want to involve compose.

This gives your devs an ultra easy setup path on local:

In production … why would you even think about deploying with compose? In general production container orchestration happens in either scripts or kubernates or some other dedicated production tool.

10

It’s only for testing instances

11

Mainly because I’ve been asked to by our team lead. His argument is when testing … he doesn’t want to rely on sysadmins, or devs knowing how to set up discourse other than doing docker-compose up -d.

1 Like
12

I agree … I followed the instructions and it didn’t take a lot of time to set up. The main issue I will have is selling the idea of running the scripts

13

I am still not following at all, maybe ask your dev manager to post here explaining why our officially supported docker dev setup is a problem.

3 Likes
14

I asked if Beginners Guide to Install Discourse for Development using Docker would suffice.

The answer was yes.

3 Likes
15

I am not associated with the OP here, but I can tell you why I want a docker compose file rather than a shell script:

  1. Shell scripts tend to not work on Windows.
  2. The shell script requires git, my docker hosts only have a bare OS and docker installed. They are, by design, incredibly lean and bare.
  3. Docker compose files can, with a little work, be converted to docker swarm files which can be run on my infrastructure and managed with docker swarm management tooling.
  4. Every other piece of my infrastructure is managed via docker-swarm tooling. Having a single piece of infrastructure that is an outlier adds a large amount of cognitive overhead that I need to store somewhere and will certainly be lost/forgotten when it comes time to upgrade (every other piece of our infrastructure gets upgrades by just updating image version in docker swarm file).

What I would like to see is a template docker swarm or docker compose file that I can use, which references an image published to Docker Hub, and I can configure by just editing the various swarm file settings.

I haven’t yet tried running the scripts locally to see if I can extract the compose file, but it sounds like that is my best bet to not have Discourse be some oddball outlier in my system. I would prefer if I didn’t need to go run a script just to generate a sample docker-compose/swarm file and if instead I could just see one in docs or a gist or something.

3 Likes
16

I want to be able to do all docker building on a separate build server to where I run in production. Why use Docker if it is a bunch of scripts that are required on the host?

On my production host I want Docker installed in swarm mode and the ability to Docker login to my registry to pull what is needed. I also want to be able to run e.g 3 instances of any container over 3 nodes (so any volumes / bind mounts to the host should be easily manageable).

Totally happy to build and do exactly the supported discourse way on staging server.

The prod docker swarm I am talking about will include many other products on the same cluster.

I plan to docker inspect all the containers on my Discourse officially supported staging server, push all pre-built docker images to a registry and try deploy them to production swarm cluster.

If I get there I will share here.

I would want to split out into multiple containers. From what I have seen, the officially supported Discourse treats Docker like VM and does everything in one container (how do you scale only one component if necessary?).

Maybe the open-sourced supported version is purposefully not orchestration manager friendly so that they can get contracts to manage deploys that require massive scale. That model sits fine by me. They should have every right to be able to make money installing Discourse to large already established production grade Swarm/Kubernetes systems.

Not saying that is how some of their income is earned, just speculating. Not important whether they are or not, just pointing out that they are in no way obligated to support anything other than their currently supported mechanisms. It must just be acknowledged that the supported method is not friendly towards a production grade container orchestration cluster.

2 Likes
17

My understanding is it for ease of support - that CDKC uses the open sourced version - they do make their income from hosting and that pays for the free support they give to the official supported version.

There is a guide to splitting the containers here Multisite configuration with Docker

We did manage to get a instance running under docker-compose so what you’re aiming for is certainly doable.

1 Like
18

Did you open-source it? Would be great to see some examples.

19

We used an older version of libre.sh / compose / discourse · GitLab as a guide. That should get you going.

2 Likes
20

Hello.
It’s May 2020 and this is still a completely contentious area of usage.

I’ve read every thread I can find on current Discourse support for docker and I’ve gone through the 5 stages of grief on this - I’m now at resignation.

Context -

I have a docker swarm that runs everything for our sites and businesses. I don’t want to buy/maintain additional VPS just to host a forum.

I just want to deploy Discourse image on it with individual containers so I can scale things differently as needed. So far I have failed. It should not be this hard.

I have done this with far more complex but comparable codebases like Gitlab and Sentry in 1-2 hours flat. This is my 3rd week of trying to get a working solution with Discourse and still no reliable installation.

Seems to me…

  • Discourse is feature rich and been around a while and has passionate and skilled contributors.
  • Discourse was an early adopter of containerisation and did what it did using both the tools and the knowledge around at the time.
  • Criticism of how it does what it does is often met with defensiveness.
  • Clear cut guidance is missing on this exact problem that many people over the last few years have asked and many more will ask in the future re: cluster orchestration.
  • Launcher etc is fine for a single docker machine, it is a beautiful script that suits a common use case. But my experience of using it create a portable image is failure.

Things that are silly…

  • the passive aggressive responses to legitimate concerns raised by people just trying to get a tiny part of their work done.
  • insisting that launcher is the ONLY way it should work.
  • referring to ‘documentation’ in threads that are out of date and expecting people to spend ages trying to read up such content to simply install something.

We can do better than this.

The ask / offer
I am willing to spend my time with someone who knows how launcher works and to create a step by step quide for creating repeatable separate container installs - with a video.

Who is up for this?

2 Likes