litmuschaos / litmus

Litmus helps SREs and developers practice chaos engineering in a Cloud-native way. Chaos experiments are published at the ChaosHub (https://hub.litmuschaos.io). Community notes is at https://hackmd.io/a4Zu_sH4TZGeih-xCimi3Q
https://litmuschaos.io
Apache License 2.0
4.37k stars 688 forks source link

Couldn't install Litmus on Arm Macos with mongodb issue #4361

Open nkguoym opened 9 months ago

nkguoym commented 9 months ago

Question

Install litmus this way with customized mongo, because using the M1 Mac. docker.io/library/mongo:latest has the arm64 version mongdb image.

 helm install chaos litmuschaos/litmus --namespace=litmus \
--set mongodb.image.registry=docker.io \
--set mongodb.image.repository=library/mongo \
--set mongodb.image.tag=latest

but got this error

/scripts/setup.sh: line 3: /opt/bitnami/scripts/mongodb-env.sh: No such file or directory
/scripts/setup.sh: line 4: /opt/bitnami/scripts/libfs.sh: No such file or directory
/scripts/setup.sh: line 5: /opt/bitnami/scripts/liblog.sh: No such file or directory
/scripts/setup.sh: line 6: /opt/bitnami/scripts/libvalidations.sh: No such file or directory
/scripts/setup.sh: line 8: is_empty_value: command not found
/scripts/setup.sh: line 12: info: command not found
/scripts/setup.sh: line 13: info: command not found
/scripts/setup.sh: line 19: is_dir_empty: command not found
/scripts/setup.sh: line 28: is_empty_value: command not found
/scripts/setup.sh: line 31: is_empty_value: command not found
/scripts/setup.sh: line 32: info: command not found
/scripts/setup.sh: line 59: /opt/bitnami/scripts/mongodb/entrypoint.sh: No such file or directory

Could you help point me on how to solve this problem?

namkyu1999 commented 9 months ago

Hi @nkguoym , Checkout readme.md

https://github.com/litmuschaos/litmus-helm

Saranya-jena commented 8 months ago

Hi @nkguoym , Can you let us know if the issue is resolved?

nikhilsethi31 commented 1 week ago

I think this issue is still present , I was also trying to install chaoscenter on my setup and got this issue , the readiness probe was failing and I got the same error