I didn’t install on Linux yet myself but my first guess was the CPU you are running on
Confirmed by Gemini -
The Cause
The phrase “Ungültiger Maschinenbefehl (Speicherabzug geschrieben)” is German for “Illegal instruction (core dumped)”. This happens when a compiled binary tries to execute a CPU instruction (such as a specific AVX, SSE, or newer x86-64 extension) that the processor does not support.
Given that the installation script runs $binary _reset and $binary doctor immediately after downloading and hits an illegal instruction on both calls, it almost certainly means the installation script downloaded a pre-compiled binary build that was compiled for a newer CPU architecture than the machine it’s running on (or possibly a mismatched architecture entirely, like an x86 binary on an older or non-standard CPU).
Suggested Fixes
Check CPU Compatibility / Flags: Have them check their CPU capabilities using lscpu or cat /proc/cpuinfo. If they are running on an older processor (such as an older Xeon, Core 2 Duo, or older AMD CPU) or inside a virtual machine that isn’t passing through the correct CPU flags, the binary will crash instantly upon hitting unsupported instruction sets.
Compile from Source (If Available): If the rabbit agent project provides source code or a way to build from source rather than pulling a generic pre-compiled release binary, building it locally will ensure it compiles specifically for the local CPU instruction set.
Check for Environment Mismatches: Ensure you aren’t accidentally trying to run an x86_64 binary on an ARM system (or vice versa), though an architecture mismatch usually yields an “Exec format error” rather than an illegal instruction. An illegal instruction strongly implies the right architecture family (e.g., x86_64), but an unsupported CPU feature level.