Using a glibc version that is different from the system-provided one shouldn't require the use of containers, as I recently heard someone claim. Let's take a look at how dynamic linking works and what the options are.

Lobsters is a community-driven platform for sharing and discussing links to articles, tutorials, and projects related to technology and programming. Readers can learn about a wide range of topics, from software development and system administration to cybersecurity and artificial intelligence. With user submissions, comments, and voting, Lobsters provides a platform for collaborative learning and knowledge sharing among technology enthusiasts.

Lobsters

Running a program against a different glibc version from the system-installed one requires understanding how dynamic binaries and glibc work. By utilizing the dynamic linker manually, you can load an alternative glibc version without crashes. Static binaries contain all program code within one executable, whereas dynamic binaries have gaps filled by shared libraries at runtime. Using tools like `patchelf`, developers can easily switch glibc versions to ensure their binaries are compatible with different system environments.

Picking glibc versions at runtime