GLIBC_2.28 not found (required by node) - node js Flex environement

[niciliketo]

Problem you have encountered:

As of 2022-05-13 our deploys to App Engine are failing.
This appears to be due to missing GLIBC

The build fails at this step.

Step #1: INFO[0036] RUN yarn install --production ||   ((if [ -f yarn-error.log ]; then       cat yarn-error.log;     fi) && false) 
Step #1: INFO[0036] cmd: /bin/sh                                 
Step #1: INFO[0036] args: [-c yarn install --production ||   ((if [ -f yarn-error.log ]; then       cat yarn-error.log;     fi) && false)] 
Step #1: node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by node)
Step #1: node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by node)
Step #1: node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by node)
Step #1: error building image: error building stage: waiting for process to exit: exit status 1

What you expected to happen:

I expect the build to succeed. Last successful build was 2022-05-11

Steps to reproduce:

• Checkout a node project that has previously been deployed to GAE.
• Run

gcloud app deploy --project=$GOOGLE_PROJECT

• NOTICE: failure with error shown above.

Other information (workarounds you have tried, documentation consulted, etc):

• Reverting to the last version of code that successfully deployed
• Checking this issue tracker - https://issuetracker.google.com
• Checking this issue tracker - https://github.com/GoogleCloudPlatform/nodejs-docker/tree/master

[jasontlouro]

@niciliketo Did you find a fix? Also experiencing this issue.

[osvald0]

Change the node version for the LTS instead use >=....

[cjsewell]

I ran in to this today while upgrading to node 18, and update on when this could be resolved?
18.12.1 is the current LTS

[slowtick]

We could not switch to nodejs 18.x in GAE flex due to this error.

Are there plans to provide official base image supporting newer nodejs LTS or using custom image for nodejs 18+ the recommended path forward?

[kennethye1]

Yes we are working on supporting the newer runtimes in the coming weeks.

[ighunter]

Any news on support for node 18?

Node 16 is end-of-life in 1 month. https://nodejs.org/en/blog/announcements/nodejs16-eol

[REPTILEHAUS]

Its still an issue, hitting it now.

[m-spyratos]

Any updates on this or support plans?