Kafka pod CrashLoopBackOff

[Knappek]

I deployed the Otel Demo on a k3s cluster with 3 worker nodes, each with 4 CPU and 8GB ram using this script on my Mac using multipass.

The kafka pod is in CrashLoopBackOff with the following log

===> User
uid=1000(appuser) gid=1000(appuser) groups=1000(appuser)
===> Setting default values of environment variables if not already set.
===> Configuring ...
Running in KRaft mode...
===> Launching ...
===> Using provided cluster id ckjPoprWQzOf0-FuNkGfFQ ...
# # A fatal error has been detected by the Java Runtime Environment: # # SIGILL (0x4) at pc=0x0000fd075073fb5c, pid=12, tid=380 # # JRE version: (21.0.2+13) (build ) # Java VM: OpenJDK 64-Bit Server VM (21.0.2+13-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, serial gc, linux-aarch64) # Problematic frame: # j java.lang.System.registerNatives()V+0 java.base # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E" (or dumping to //core.12) # # An error report file with more information is saved as: # /tmp/hs_err_pid12.log [0.239s][warning][os] Loading hsdis library failed # # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. #

I don't know what this means. Can somebody help me and give me a hint?

[julianocosta89]

Hey @Knappek did you happen to solve this issue?
I was going through the discussions and saw that we never came back to you (apologies for that).