IronPdf.UpdatedChrome on Linux with glibc 2.31
From 2026.11.1, IronPdf.UpdatedChrome on Linux runs Chromium 146, which needs glibc 2.31 or newer on x64 (2.34 on ARM64) and uses the operating system's NSS libraries instead of bundled copies. On an older distribution, IronPDF can't load the engine, tries to download other engine files, then stops at the first render. On an image without NSS, the engine fails to load.
FATAL:gpu_data_manager_impl_private.cc(440)] GPU process isn't usable. Goodbye. The IronPdf Chrome renderer in '/app' needs glibc 2.30 or newer, but this system has glibc 2.27. The IronPdf.UpdatedChrome packages need glibc 2.31 or newer on Linux (Ubuntu 20.04, Debian 11, RHEL 9, Amazon Linux 2023 or later)… libnspr4.so: cannot open shared object file: No such file or directory
Chromium 146 is built against a newer glibc, so its native files can't load on older systems, and the default engine files IronPDF then downloads can't run alongside them. Up to 2026.10, the x64 UpdatedChrome package bundled its own NSS, NSPR and SQLite; from 2026.11.1 it uses the system copies, so OS security updates cover them. On ARM64, every IronPDF engine already needed glibc 2.34 before this release.
Three distinct failures come from the same root:
- The first error appears on older distributions such as Ubuntu 18.04, Debian 10 and Rocky 8, while Amazon Linux 2 exits with no message.
- The second appears instead, after several minutes, when the machine can't reach nuget.org.
- The third appears when NSS is missing.
A later IronPDF release is planned to show the glibc message directly.
Solution
1. Check the glibc version
Confirm what the machine or base image provides:
ldd --version
You need 2.31 or higher on x64, or 2.34 or higher on ARM64. If it's lower, skip to step 3.
2. Install the system libraries
LinuxAndDockerDependenciesAutoConfig is on by default, so an application running as root installs the libraries at the first render, which then takes a few minutes longer. If the application doesn't run as root, or auto-configuration is off, install them in your image.
For Debian and Ubuntu (tested on Debian 12):
RUN apt-get update && apt-get install -y \
libgtk2.0-0 libatk-bridge2.0-0 libx11-xcb1 libxcb-dri3-0 libgbm1 \
libasound2 libxrender1 libfontconfig1 libxshmfence1 libxkbcommon0 \
libnss3 libudev1
For RHEL 9 / Rocky / Alma 9 and Amazon Linux 2023 (tested on Rocky Linux 9 and Amazon Linux 2023):
dnf install -y nss systemd-libs at-spi2-atk libXcomposite libXrandr libXdamage \
mesa-libgbm alsa-lib pango cups-libs libxshmfence libxkbcommon
NSS alone isn't enough: with only NSS installed, the next error is libatk-1.0.so.0: cannot open shared object file. If libudev1 (systemd-libs) is missing, the process stops with a bare Trace/breakpoint trap.
3. Pick a path when glibc is too old
If glibc is older than the minimum, choose one of the following.
Move to a supported OS or base image: Ubuntu 22.04, Debian 12, RHEL 9, Amazon Linux 2023, or public.ecr.aws/lambda/dotnet:8 for AWS Lambda.
Keep the OS and get Chromium 146 through Docker: switch to the IronPdf.Slim package and run the engine container, which brings its own OS. Use the same <version> as your IronPDF client package.
docker run -d -p 127.0.0.1:33350:33350 ironsoftwareofficial/ironpdfengine:<version>-updatedchrome
To build your own image, use FROM ironsoftwareofficial/ironpdfengine:<version>-updatedchrome. Copying the engine files onto another base image needs the same glibc minimum and the libraries from step 2.
Keep the OS and render in-process (x64 only): switch to the default IronPdf.Linux package, which uses Chromium 109. On ARM64 this doesn't help, because the default package also needs glibc 2.34.
Short-term only (x64): pin IronPdf.UpdatedChrome.Linux 2026.10.3 (Chromium 131), which still bundles NSS. That engine gets no further updates.
What Doesn't Work
- Alpine and other musl-based images have no glibc, so UpdatedChrome can't run in-process there.
- Upgrading only IronPDF on Ubuntu 18.04, Debian 10, CentOS/RHEL 7 to 8 or Amazon Linux 2 fails, because no Chromium 146 build exists for these systems.
References
- IronPDF on Linux
- IronPDF advanced NuGet installation
- Deploying IronPDF to AWS Lambda with Docker (libnss3)
Curtis Chau holds a Bachelor’s degree in Computer Science (Carleton University) and specializes in front-end development with expertise in Node.js, TypeScript, JavaScript, and React. Passionate about crafting intuitive and aesthetically pleasing user interfaces, Curtis enjoys working with modern frameworks and creating well-structured, visually appealing manuals.