Upgrading from node:12-alpine to node:18-alpine breaks glibc setup (2.31-r0 no longer works)

[shrihariONX]

Hi, thanks for maintaining this project.

I've recently upgraded our base image from node:12-alpine to node:18-alpine.

Previously, we were using glibc-2.31-r0 successfully with node:12-alpine like so:

**ENV GLIBC_VER=2.31-r0

RUN apk --no-cache add binutils curl \
    && curl -sL https://alpine-pkgs.sgerrand.com/sgerrand.rsa.pub -o /etc/apk/keys/sgerrand.rsa.pub \
    && curl -sLO https://github.com/sgerrand/alpine-pkg-glibc/releases/download/${GLIBC_VER}/glibc-${GLIBC_VER}.apk \
    && apk add --no-cache glibc-${GLIBC_VER}.apk

This worked perfectly for installing and running binaries like AWS CLI v2.**

However, after switching to node:18-alpine, the same setup fails at runtime with **errors.**

Is there a glibc version compatible with node:18-alpine (which uses Alpine 3.18+), or do you recommend sticking to a specific Alpine version (like 3.17) for glibc compatibility?

Any help or guidance would be appreciated.