# Discourse run error in k8s
**URL:** https://meta.discourse.org/t/discourse-run-error-in-k8s/224732
**Category:** Self-hosting
**Tags:** unsupported-install
**Created:** [April 19, 2022, 11:38am UTC](https://meta.discourse.org/t/discourse-run-error-in-k8s/224732 "2022-04-19T11:38:48Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Yaoqi\_Yan](https://meta.discourse.org/u/Yaoqi_Yan)
#### Post date: [April 19, 2022, 11:38am UTC](https://meta.discourse.org/t/discourse-run-error-in-k8s/224732/1 "2022-04-19T11:38:48Z")
I would like to install discourse in K8s. The Docker works well in local environment but report bellow error after upload to k8s. Looks like related to postures and redis. Can anybody help?
run-parts: executing /etc/runit/1.d/00-ensure-links
run-parts: executing /etc/runit/1.d/00-fix-var-logs
run-parts: executing /etc/runit/1.d/01-cleanup-web-pids
run-parts: executing /etc/runit/1.d/anacron
run-parts: executing /etc/runit/1.d/cleanup-pids
Cleaning stale PID files
run-parts: executing /etc/runit/1.d/copy-env
Started runsvdir, PID is 47
ok: run: redis: (pid 61) 0s
ok: run: postgres: (pid 62) 0s
chgrp: invalid group: ‘syslog’
supervisor pid: 57 unicorn pid: 114
config/unicorn\_launcher: line 71: kill: (114) - No such process
config/unicorn\_launcher: line 15: kill: (114) - No such process
(57) exiting
timeout: down: redis: 0s, normally up, want up
ok: run: redis: (pid 169) 0s
timeout: down: postgres: 1s, normally up, want up
timeout: down: redis: 0s, normally up, want up
timeout: down: redis: 0s, normally up, want up
timeout: down: redis: 1s, normally up, want up
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 20, 2022, 3:42am UTC](https://meta.discourse.org/t/discourse-run-error-in-k8s/224732/2 "2022-04-20T03:42:58Z")
> [@Yaoqi\_Yan](#):
>
> I would like to install discourse in K8s.
That’s not supported here. There are too many things that might be wrong to be able to support anything other than the [standard install](https://meta.discourse.org/t/142537?silent=true). Unless you’re sure to need scaling for a community that has periods of much higher activity than others you really don’t need k8s.
Did you build an image with launcher or are you using bitnami? If it’s bitnami, you can get support from them.
---
### Author:  [@Yaoqi\_Yan](https://meta.discourse.org/u/Yaoqi_Yan)
#### Post date: [April 20, 2022, 5:55am UTC](https://meta.discourse.org/t/discourse-run-error-in-k8s/224732/3 "2022-04-20T05:55:03Z")
build with launcher ~~~
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 21, 2022, 9:18am UTC](https://meta.discourse.org/t/discourse-run-error-in-k8s/224732/4 "2022-04-21T09:18:45Z")
You’d need to use an external postgres and redis. It looks like you’re trying I use a container that includes redis and postgres?
---
### Author:  [@Yaoqi\_Yan](https://meta.discourse.org/u/Yaoqi_Yan)
#### Post date: [April 24, 2022, 3:51am UTC](https://meta.discourse.org/t/discourse-run-error-in-k8s/224732/5 "2022-04-24T03:51:00Z")
It works with external rids and Postgres. Thanks Jay!
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 24, 2022, 6:17am UTC](https://meta.discourse.org/t/discourse-run-error-in-k8s/224732/6 "2022-04-24T06:17:47Z")
Great! Glad you’re up and running!