Hi,
I am trying to deploy the discourse base image into a kubernetes cluster.
The build of the base image works but obviously the CMD part that should start the launcher is missing.
I already tried to search the launcher on /var/discourse, but I am unable to find it (root looks like a normal ubuntu root directory…).
Does anyone know where the launcher is located within the docker base image?
Thank you for your support 
LG
You can’t. You’ll need to create a custom image that has a little more stuff in it than the base image includes. For some hints on what you’ll need to do, see Can Discourse ship frequent Docker images that do not need to be bootstrapped? for starters.
I’m working on the same problem and hope to have a solution (that solves my specific set of problems) in the next month. I won’t share it here because it’ll be a support nightmare that meta is not designed to handle. At some point I will consider making those images available, but only when I’m sure that meta won’t be flooded with support requests.
@pfaffman, How has finding the solution to this problem gone? Any other tips and tricks? I’m about to dive down this rabbit hole myself.
I think I’ve got it figure out, though I haven’t yet automated it. I’ve got several other things going on that have that pushed back a bit. If you have a budget, I’d be happy to help out. You can PM me or see contact info in my profile.
@technik, Did you get the base image deployed on Kubernetes? Any tips or issues you’d like to share?
this is very interesting, would love to learn more about this
Had I gotten here first, I’d likely have closed this. 
What is interesting? What do you want to know about and why?
Kubernetes will (almost certainly, though it’s not up to me) never be supported. I’m working with someone this week who needs help with their k8s deployment. If you’ve got a budget, you’re welcome to contact me.
I would love to learn more about every part of it.
Agreed, it will probably never be supported and I would not expect that. The Discord team provides something amazing as it is, I I wouldn’t expect them to support more than they do.
But that is also precisely why forums are great, we can exchange knowledge and support each other where otherwise this would be much more difficult.
I like Discourse a lot, and solving things like deploying from “scratch” IMO is a nice way to learn more about a system.
In broad strokes, if you did want to crank up Discourse with k8s, you’d start with a normal two-container install (or look at topics about using an external database), build an image with launcher, then push that image to a repo. You can use ./launcher start-cmd web_only to see what ENV variables you’d need to pass to the container to make it work.
If you have a specific question, you can open a new topic.