Skip to content
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

[Helm Install Failed] An exception occurred during the deployment of the ES service. #649

Open
cheny-alf opened this issue Nov 24, 2024 · 3 comments

Comments

@cheny-alf
Copy link
Contributor

What happened?

image
Here's some additional information that might be helpful in diagnosing the issue:

kubectl describe pod elasticsearch-864cd54956-q997n -n karpor

image

kubectl logs elasticsearch-864cd54956-q997n -n karpor

image

What did you expect to happen?

null

How can we reproduce it (as minimally and precisely as possible)?

I started the deployment entirely according to the document at https://www.kusionstack.io/zh/karpor/getting-started/quick-start.

Anything else we need to know?

No response

Karpor version

$ karpor -V
# v0.5

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

@elliotxx
Copy link
Collaborator

@cheny-alf Can you share your operating system and architecture? There is a possibility that the image architecture does not match

@cheny-alf
Copy link
Contributor Author

@cheny-alf Can you share your operating system and architecture? There is a possibility that the image architecture does not match

os: macOS 15.0
architecture: ARM64
chip: M4

@elliotxx
Copy link
Collaborator

@cheny-alf I don't have an M4 Mac on hand, so it's a bit difficult to reproduce. I'm okay on an M3 Mac.

I guess there are two possible reasons:

  1. One is architecture mismatch. You can try cloning the charts repository locally, modifying the elasticsearch image in the karpor chart, adding the suffix -arm64, and finally manually installing the local charts.
  2. The second type is due to insufficient running specifications and being killed by the system process. You can check the specifications and limitations of Docker Desktop.

Example:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants