I’d like to try IN and want to create an API Key. I’m doing this on a virtual machine with the current github version (commit 9941847) at date 2024/10/01.
According to the readme, this is done via:
# docker run --rm -it invoiceninja/invoiceninja php artisan key:generate --show
it definitely seems to be a hardware issue. Also the mysql - container breaks when trying to start it via
docker-compose up -d
docker logs ninja_db
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
Fatal glibc error: CPU does not support x86-64-v2
...
docker logs ninja_app
2024-10-01T14:40:42Z [INFO] [Entrypoint]: Initialising Invoice Ninja...
Segmentation fault
2024-10-01T14:40:44Z [INFO] [Entrypoint]: Initialising Invoice Ninja...
Segmentation fault
2024-10-01T14:40:45Z [INFO] [Entrypoint]: Initialising Invoice Ninja...
Segmentation fault
...
When configuring the maximum CPU features from the VMHost (Host CPU: Xeon E5-2680 v2 introduced 2013) for the virtual machine, the mysql container comes up, but the ninja application still segfaults.
I set up a new virtual machine on newer VMHost (Host CPU: Xeon E5-2680 v4 introduced 2016). The ninja_app container works out of the box. When I activate the CPU-Feature-Set x86-64-v2 on the newer Host, the ninja_db container comes up successfully.