-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup Pixie locally with Colima fails to initialise ElasticSearch #1858
Comments
Any idea? |
Anyone? |
The version of Elasticsearch in the stackoverflow you linked is 7.10.2. Pixie currently uses 7.6. It's possible this is an issue with elasticsearch that got fixed between 7.6 and 7.10.2. You could try changing this line
to use the image suggested in the stackoverflow post. |
@JamesMBartlett If I change the image to the one from the StackOverflow answer I get
Not sure if it might be because the one from the SO answer is a public image, while the Pixie one is a patched image |
Ok, I managed to make it work removing the
|
Hello team,
First, I'd like to say that I'm very excited to try out Pixie
I was trying to install locally on a local Kubernetes cluster on top of Colima, is it supported? I was not sure but I tried anyway as this is how the local development happens at my company
I'm running on a MacOS M3 Max with Sonoma 14.4
Colima version
Then I have the first issue on the
Install Pixie Cloud
sectionA few pods in CrashLoopBackoff
It seems to be a cascade issue due to the elastic search pods crashing
Logs from the elastic search:
I tried to continue the setup, but then I get other errors, I believe this one should be fixed first
For example, running dev_dns_updater gets stuck after typing the password
Any idea what could be causing ElasticSearch failure? What I found googling was related to not working on Apple Silicion, but it seems that since then it was fixed: https://stackoverflow.com/questions/65962810/m1-mac-issue-bringing-up-elasticsearch-cannot-run-jdk-bin-java
The text was updated successfully, but these errors were encountered: