Skip to content

Documentation / Knowledge Base

Enclave fails to start on Linux after upgrading

Symptoms

After upgrading Enclave, the enclave binary fails to start with errors referencing missing GLIBC or GLIBCXX versions:

enclave: /lib/arm-linux-gnueabihf/libm.so.6: version `GLIBC_2.29' not found (required by enclave)
enclave: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by enclave)
enclave: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.34' not found (required by enclave)

The exact version numbers and library paths may vary depending on your architecture and distribution.

Cause

Enclave versions released from 2026 onwards are built using the .NET 10 runtime, which requires a newer version of the GNU C Library (glibc) than the previous .NET 8 runtime. If your Linux distribution ships a glibc version older than the runtime requires, the Enclave binary will not start.

The minimum glibc version depends on your system architecture. 32-bit ARM (armv7l) systems are the most affected, requiring glibc 2.34 or later. The x64 and arm64 runtimes have a lower glibc floor and are compatible with a wider range of distributions.

Affected distributions

The following table lists distributions which were previously supported but are no longer compatible with current versions of Enclave:

Distribution glibc version Status
Ubuntu 16.04, 18.04, 20.04 2.23 – 2.31 Not supported
Debian 10 (Buster), 11 (Bullseye) 2.28, 2.31 Not supported
Raspbian 10 (Buster), 11 (Bullseye) 2.28, 2.31 Not supported
CentOS / RHEL 7 2.17 Not supported
Amazon Linux 2018.03, Amazon Linux 2 2.26 Not supported

Resolution

Upgrade your operating system to a supported distribution. The current minimum supported versions are listed on our Linux setup page. The key minimums are:

Distribution Minimum version
Ubuntu 22.04 LTS
Debian 12 (Bookworm)
Raspbian 12 (Bookworm)
CentOS / RHEL 8 (x64), 9 (arm64)
Amazon Linux 2023
openSUSE Leap 15.6
SLES 15.6
Fedora 38

Raspberry Pi users

The Cortex-A53 (and newer) processors found in Raspberry Pi 3 and later models are 64-bit capable. If your Pi is running a 32-bit OS (reported as armv7l by uname -m), consider installing the 64-bit version of Raspberry Pi OS (Bookworm or later) and using the linux-arm64 package instead. This provides better long-term compatibility with the .NET runtime.

You can check your current glibc version by running:

ldd --version

Upgrading from Buster to Bookworm

Raspberry Pi OS does not support skipping major versions. If you are running Buster (Debian 10) you must upgrade through Bullseye (Debian 11) first, then from Bullseye to Bookworm (Debian 12). Back up your system and any Enclave configuration (in /etc/enclave/) before starting. Refer to the official Raspberry Pi documentation for upgrade instructions.


Having problems? Contact us at support@enclave.io or get help and advice in our community support channels.

Published February 3, 2026