-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Build
-
Fully Compatible
-
ALL
SERVER-84539 updated bazel compilation to use the glibc version of the host and updated the downloaded compiler dependencies to link against compatible version of glibc (from amazonlinux2).
Because bazel now uses the host's glibc, this now makes it link against the remote execution container's glibc when remote execution is enabled.
The remote execution container is currently dockerhub's gcc-bookworm container. Bookworm is a newer release of the debian distribution, which uses glibc 2.36. This version is incompatible with certain distros we still support (ex. amazon linux 2, rhel8.2, etc)
In other words, the RE container links bazel built libraries against glibc 2.36. When the built libraries are executed on hosts that use glibc 2.26, it fails because glibc isn't forwards compatible.
Switch the remote execution container to use a distro that has a version of glibc that's old enough to be compatible with all of our supported distros.