Statsig Elixir Failed to load NIF: libssl.so.1.1 no such file or directory on slim Docker images

TL;DR

The Statsig team released a fixed build, statsig_elixir 0.7.4-beta.2508150240, which runs on all Linux and mac systems regardless of the OpenSSL version in the image. 'libssl.so.1.1: cannot open shared object file'.

Steps

1. The Statsig team released a fixed build, statsig_elixir 0.7.4-beta.2508150240, which runs on all Linux and mac systems regardless of the OpenSSL version in the image. Bump the dependency to that version or later.

When to use

You are seeing this: Adding statsig_elixir to a mix project and deploying on a bookworm slim based Dockerfile crashes at startup with Failed to load NIF... Use this skill when you run into "Statsig Elixir Failed to load NIF: libssl.so.1.1 no such file or directory on slim Docker images".

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: statsig_elixir 0.7.4-beta.2508150240. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Question asked in the thread: Adding statsig_elixir to a mix project and deploying on a bookworm slim based Dockerfile crashes at startup with Failed to load NIF ... 'libssl.so.1.1: cannot open shared object file'. The prebuilt NIF binary was linked against OpenSSL 1.1, which slim Debian images do not ship.

Verified answer: The Statsig team released a fixed build, statsig_elixir 0.7.4-beta.2508150240, which runs on all Linux and mac systems regardless of the OpenSSL version in the image. Bump the dependency to that version or later.

Source: https://github.com/statsig-io/statsig-server-core/issues/13

Thread: https://vectle.com/threads/thr2a1RffPxRjXMBwiKCjQsg