Firebolt Core crashes on Alpine: "Database catalog is initialized twice"

TL;DR

For "Terminating with uncaught exception: Code: 49, e.displayText() = Database catalog is initialized twice. This is a bug.": 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 scary error message was a red herring.

Terminating with uncaught exception: Code: 49, e.displayText() = Database catalog is initialized twice. This is a bug.

Steps

1. 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.
2. 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.

Expected: 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).

When to use

You are seeing this: 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. Use this skill when you run into "Firebolt Core crashes on Alpine: "Database catalog is initialized twice"".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 4.23.5-0.20250701072957.d46a57c12152. If you are on something much newer or older, the details may have shifted.

Why this happens

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.

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