-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
immich_server startup fails with Fatal error in , line 0. unreachable code #12133
Comments
Can you provide some more detail about what sort of system you're running on? |
I am trying Docker on Alpine for the first time, and this is my first docker container on it. |
I want to add a data point: After getting Immich up and running on v1.108.0, I configured an external library and loaded in a little over 10K photos. I then tried upgrading Immich to release, but it crashes with the same error. So it's not something that happens only on initial startup on a fresh install. |
Both alpine/freebsd and bhyve are kind of unusual layers (as opposed to most people using linux/kvm and such) and I'm inclined to suspect those - though I don't know enough about them to back that up. |
Unusual sure, but it shouldn’t make any difference what the virtualization hypervisor is especially if I’m not doing anything fancy like PCI pass through. I have NextCloud and Paperless-ngx running on Docker in an Ubuntu VM on the same hypervisor. I guess I can give a Debian VM a shot, but only Alpine’s kernel is relevant to something running inside Docker, right? It’s not like Alpine’s stripped down libc should come into play here. |
Same issue under Debian 12.6 with Immich 1.113.0
|
This kind of looks like nodejs/node#51555, but adding |
I’m having the exact same problem with a remarkably similar setup. immich running under Docker on an Ubuntu server VM on bhyve on TrueNAS 13 (FreeBSD) on a Ryzen 5600X. |
Oh my god. I think I found a workaround. I had the VM that was running Immich inside Docker setup in bhyve to have multiple "Virtual CPUs" rather than 1 virtual CPU with multiple cores/threads. The fact that this was failing right after the CPU detection log line was in fact related. When I switched over to having one virtual CPU with multiple cores, it stopped crashing. (My TrueNAS is relatively old, I think the virtual CPU setting was set by some migration.) @lpummer I strongly suspect that this will fix your problem as well. |
The bug
Trying out Immich for the first time, following the Docker Compose instructions, the
immich_server
container keeps restarting. The output ofdocker logs -f immich_server
is given in the Logs section.The crash at startup started with v1.109.0 and continues through v1.112.1, though the strack traces look a little different under v1.109.0. I've pasted what I see in v1.112.1. By editing IMMICH_VERSION I was able to find that v1.108.0 is the last version that starts up reliably.
The OS that Immich Server is running on
Linux version 6.6.47-0-virt (buildozer@build-3-20-x86_64) (gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309, GNU ld (GNU Binutils) 2.42) #1-Alpine SMP PREEMPT_DYNAMIC 2024-08-19 08:18:35
Version of Immich Server
v1.112.1
Version of Immich Mobile App
n/a
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered: