Immutable solution version
Firebolt Core crashes on Alpine: "Database catalog is initialized twice"
Complete solution
How to fix: Firebolt Core crashes on Alpine: "Database catalog is initialized twice". The scary error message was a red herring. A Firebolt engineer dug into the logs and found the real root cause: an internal component polls `/proc/pressure/memory` for memory pressure info, and that kernel interface doesnt exist on Alpine, so startup failed.
The problem
Starting the Firebolt Core Docker image on Alpine Linux crashed immediately with Terminating with uncaught exception: Code: 49, e.displayText() = Database catalog is initialized twice. This is a bug. The reporter was mounting a data volume and passing --security-opt seccomp=unconfined as documented. The catalog error turned out to be a red herring: an internal component polls /proc/pressure/memory, which doesnt exist on Alpine, so startup failed.
What fixed it
The scary error message was a red herring. A Firebolt engineer dug into the logs and found the real root cause: an internal component polls /proc/pressure/memory for memory pressure info, and that kernel interface doesnt exist on Alpine, so startup failed. The "catalog is initialized twice" crash came from the fallback exception server that was supposed to report the real error but crashed itself.
Both were fixed in the Firebolt Core image 4.23.5-0.20250701072957.d46a57c12152 (the first attempt at a fixed image had to be pulled, this is the good one). The reporter confirmed "It's working now". So: pull a current image and the Alpine startup crash goes away.
Evidence
A user asked: Starting the Firebolt Core Docker image on Alpine Linux crashed immediately with Terminating with uncaught exception: Code: 49, e.displayText() = Database catalog is initialized twice. This is a bug. The reporter was mounting a data volume and passing --security-opt seccomp=unconfined as documented. The catalog error turned out to be a red herring: an internal component polls /proc/pressure/memory, which doesnt exist on Alpine, so startup failed. The verified answer: The scary error message was a red herring. A Firebolt engineer dug into the logs and found the real root cause: an internal component polls /proc/pressure/memory for memory pressure info, and that kernel interface doesnt exist on Alpine, so startup failed. The "catalog is initialized twice" crash came from the fallback exception server that was supposed to report the real error but crashed itself.
Both were fixed in the Firebolt Core image 4.23.5-0.20250701072957.d46a57c12152 (the first attempt at a fixed image had to be pulled, this is the good one). The reporter confirmed "It's working now". So: pull a current image and the Alpine startup crash goes away. Thread: https://vectle.com/threads/thr_XJZUDsyp7M4LQ697-i2Nhw
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_VvowKp1IBr6QDcaYIqzklw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Firebolt Core crashes on Alpine: "Database catalog is initialized twice" <span>— Vectle</span></a>