Description
The floci-ui container crashes immediately on startup with exit code 132
(SIGILL / Illegal instruction). The main floci (AWS emulator) container
runs fine and reports "healthy" — only floci-ui fails.
Environment
- Image:
floci/floci-ui:latest
- Host OS: Linux (via Portainer / Docker)
- CPU: Intel Xeon W3540 (Nehalem microarchitecture, released 2009)
- CPU instruction set: SSE, SSE2, SSSE3, SSE4.1, SSE4.2 — no AVX, no AVX2, no BMI2
- Architecture: x86_64 / linux-amd64 (confirmed matching, not an arch mismatch)
Steps to reproduce
- Run
floci/floci:latest + floci/floci-ui:latest via docker-compose
(or Portainer stack)
- Observe
floci-ui container status
Expected behavior
floci-ui starts normally and serves the console UI.
Actual behavior
Container exits with code 132 immediately after starting. No further logs
are produced beyond the crash.
Root cause (as far as I can tell)
packages/api in floci-ui appears to run on Bun. Bun's runtime requires
AVX CPU instructions (even the "baseline" Bun build still requires AVX,
just not AVX2), and crashes with SIGILL on CPUs that lack AVX entirely —
which is the case here (pre-Sandy Bridge Intel CPUs, like this Nehalem
Xeon).
This is a known Bun limitation, documented in several other projects that
recently moved to Bun runtime and hit the same issue:
Suggested fix / request
Would it be possible to:
- Provide a Node.js-based fallback build (similar to
floci/floci:*-jvm
tags that exist for the main emulator image), or
- Document this CPU requirement clearly in the README/installation docs, or
- Detect the missing AVX support and fail with a clear error message
instead of a bare SIGILL crash
Happy to test any proposed fix on this hardware if useful.
Description
The
floci-uicontainer crashes immediately on startup with exit code 132(SIGILL / Illegal instruction). The main
floci(AWS emulator) containerruns fine and reports "healthy" — only
floci-uifails.Environment
floci/floci-ui:latestSteps to reproduce
floci/floci:latest+floci/floci-ui:latestvia docker-compose(or Portainer stack)
floci-uicontainer statusExpected behavior
floci-uistarts normally and serves the console UI.Actual behavior
Container exits with code 132 immediately after starting. No further logs
are produced beyond the crash.
Root cause (as far as I can tell)
packages/apiin floci-ui appears to run on Bun. Bun's runtime requiresAVX CPU instructions (even the "baseline" Bun build still requires AVX,
just not AVX2), and crashes with SIGILL on CPUs that lack AVX entirely —
which is the case here (pre-Sandy Bridge Intel CPUs, like this Nehalem
Xeon).
This is a known Bun limitation, documented in several other projects that
recently moved to Bun runtime and hit the same issue:
Suggested fix / request
Would it be possible to:
floci/floci:*-jvmtags that exist for the main emulator image), or
instead of a bare SIGILL crash
Happy to test any proposed fix on this hardware if useful.