Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error at starting apachepulsar/pulsar-dashboard docker container within Kubernetes

See original GitHub issue

Hi there!

Issue I’ve used the helm chart available in the 2.4.2 Apache Pulsar project. Every pod is created and running correctly except pulsar-dashboard which has the CrashLoopBackOff status.

It looks like the initdb file from postgresql does not exist. Here what the logs are saying :

Starting Pulsar dasboard
+ /pulsar/init-postgres.sh
+ rm -rf '/data/*'
+ chown -R postgres: /data
+ chmod 700 /data
+ sudo -u postgres /usr/lib/postgresql/9.6/bin/initdb /data/
sudo: /usr/lib/postgresql/9.6/bin/initdb: command not found

To Reproduce Simply install the helm chart with values-mini.yaml and look at the pods in the pulsar namespace. To be sure, I’ve tried to run the container alone on my machine and I get the same error.

Expected behavior I would expect Pulsar Dashboard to run properly 😃

Cluster Kubernetes:

Server version 1.12 on linux/amd64 platform

Issue Analytics

State:
Created 4 years ago
Reactions:2
Comments:14 (5 by maintainers)

Top GitHub Comments

2reactions

dockerzhangcommented, Dec 18, 2019

there is a bug in apachepulsar/pulsar-dashboard:2.4.2 docker image, /usr/lib/postgresql/9.6/bin/initdb - > /usr/lib/postgresql/11/bin/initdb for /pulsar/init-postgres.sh perhaps you can set image tag to other version, apachepulsar/pulsar-dashboard:2.4.1 works fine for me.

1reaction

tshhcommented, Dec 13, 2019

running into same problem too. use “kubectl set image deployment” set image to pulsar-dashboard:2.3.0 is ok.

then I have another problem: https://github.com/apache/pulsar/issues/5849