NextJS 13 Vercel build failing. React-pdf

[ewaninfo]

Summary

I'm using react-pdf. Everything works as expected locally.

Here is the error that is causing the Vercel build to fail:

Error: /lib64/libc.so.6: version 'GLIBC_2.28' not found (required by /vercel/path0/pwa/node_modules/canvas/build/Release/libglib-2.0.so.0)

Canvas is a dependency of pdf.js, which is a dependency of react-pdf.

Just wondering if anyone has experienced the same/similar issue? Any suggestions would be very welcome.

Example

No response

Steps to Reproduce

Environment:
react: 18.2.0
next: 13.1.6
react-pdf: 7.1.2
node: 18.x

Create a NextJS app
Install react-pdf
Push the branch to Vercel

[smaeda-ks]

Hi, we're aware of this issue, and the only workaround as of today is to downgrade Node version to 16.x. Could you try that?

We're actively discussing how we can support those GLIBC versions in Node 18.x, and we will deliver updates when we have an update to share.

[lancejpollard]

@smaeda-ks FWIW I was able to get node-canvas to build on Node 20 but not Node 18 on Vercel. However, Node 20 has issues with yum install x (installing any yum package) in a custom install script, so there are other problems with v20.

Any update on getting it to work with Node 18?

[tisonkun]

@smaeda-ks is there a doc page telling which GLIBC versions are supported?

[j-wing]

Hi @smaeda-ks, wanted to check in on this. It sounds like the only options right now are to downgrade to a deprecated node version or upgrade to a beta one. Any news on plans to bring this fix to Node v18, since it's the only stable option right now?

[qianrum]

@smaeda-ks I also want to check in on this. Given that new builds for Node.js 16.x will no longer be available after June 14, 2014, I wonder if you have plans to address this issue. Really appreciate your help.

[2pmflow]

Hi @smaeda-ks , wondering if there were any updates here, given node16 being disabled in less than two months. Appreciate your help!

[AidanLaycock]

We are running into the same issue (Not due to this specific package). Is there a timeline on when the image will be updated as EoL is about 6-7 weeks away now (https://vercel.com/changelog/node-js-14-and-16-are-being-deprecated) on Vercel.

As this is preventing us from upgrading some other services as well.

[smaeda-ks]

Right, totally valid concern, I agree. Extending the Node 16.x support is also on our table but it's hasn't decided yet. We will keep you updated in future updates. Thank you for your patience.

[AidanLaycock]

We have found an odd issue with this when trying to spin up the same codebase on a new vercel project (As we wanted to test that it wasn't an upgrade issue). And we did find that for one of our projects it did actually work with Node 18 on a new project. So I am not sure if this is also related to a pool of images, with some having issues rather than all of them.

Do let us know if there is anything we can do to help, as we want to see this fixed as soon as possible.

[weidezhang]

running into the same issue. also due to the canvas lib required by pdf-js.

[lancejpollard]

Same, using node-canvas via react-pdf.

[digredeth]

Im running into the same issue, the problem is that I cant downgrade node js version since I'm using langchain and it require node >= 18

[digredeth]

I'm running trough Render right now

[ethtea]

+1, also running into

Error: /lib64/libc.so.6: version  'GLIBC_2.28' not found (required by /vercel/path0/pwa/node_modules/canvas/build/Release/libglib-2.0.so.0)

after upgrading to node 18, currently downgrading to 16

[wewlad-dev]

Same issue when building Zola 0.17.2 on vercel, I don't use Node but still have the problem.
zola: /lib64/libm.so.6: version GLIBC_2.27 not found (required by zola)

Folks at Zola said the image used by vercel is an old image getzola/zola#1713 (comment)

Vercel's builders run in an amazonlinux container, which uses outdated glibc. I tried to build zola 0.15.3 from source in that environment, and it works fine.

Update: I used Netlify instead

[jameslawson]

I also encountered a similar error when starting my first Vercel project, I have a monorepo and depend on @moonrepo/cli.
My monorepo scripts/commands currently target Node v20.4.0, pnpm v8.6.7

/vercel/path0/node_modules/.bin/../@moonrepo/cli/moon: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /vercel/path0/node_modules/.bin/../@moonrepo/cli/moon)
--
09:13:26.509 | /vercel/path0/node_modules/.bin/../@moonrepo/cli/moon: /lib64/libc.so.6: version `GLIBC_2.29' not found (required by /vercel/path0/node_modules/.bin/../@moonrepo/cli/moon)
09:13:26.510 | /vercel/path0/node_modules/.bin/../@moonrepo/cli/moon: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /vercel/path0/node_modules/.bin/../@moonrepo/cli/moon)
09:13:26.510 | /vercel/path0/node_modules/.bin/../@moonrepo/cli/moon: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by /vercel/path0/node_modules/.bin/../@moonrepo/cli/moon)
09:13:26.524 | Error: Command "npx moon run jx-frontend:build-production" exited with 1

I don't want to go through my monorepo and downgrade everything. I might try and deploy via a GitHub action as GitHub's machines support latest node for running my build commands. i.e. going to try this next: https://vercel.com/guides/how-can-i-use-github-actions-with-vercel#configuring-github-actions-for-vercel then probably give up on vercel unless anyone has any ideas

[pgzmnk]

Facing a similar issue when deploying a nextjs app to Vercel. The API routes that depend on the duckdb library error, while the other API routes work successfully. Downgraded node from 18.x to 16.x and the error persists.

Error: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /var/task/node_modules/duckdb/lib/binding/duckdb.node)

Thoughts appreciated.

[pgzmnk]

Disregard. This seems to be duckdb specific: https://github.com/duckdb/duckdb/issues/7088

[maderesponsively]

I'm receiving the same 'Error: /lib64/libc.so.6: version `GLIBC_2.28' not found' error. I'm using Next.js and Canvas. It's a bit worrying to see that v16 is going to be deprecated early next year. I don't want to have to move from Vercel hosting as it's great.

[wi-ski]

Deal breaker atm

[jbednar97]

Issue resolved with this, but had similar issue with Node version. Using 16x fixed the problem, but it's really not great to see when the 16x version is about do be deprecated really soon

[abhinavtalentinc]

Hi @smaeda-ks ,

We have a use-case similar to @ewaninfo and some of the other members in this discussion. The workaround of using 16x has also worked for us for upgrading from 14x. We would appreciate if you could update the thread once a fix has been planned for this issue, so that we can plan upgrading our app to 18x accordingly.

[joost-berg]

Any update on this issue? I really want to use node 18 asap.

[dataconcept-it]

@smaeda-ks Any update on this issue? We are running into more and more issues because we cannot update our app to node 18x. The deprecation date is also not too far away anymore. Thanks in advance :)

[joost-berg]

Updating to nextjs 14 is also not possible with node 16x, so the problem is getting more and more urgent.

[mohaahadji]

I am getting the same issue! any update please?

[mohaahadji]

Yes that's exactly what's happened to me, still cannot figure out the issue!

[emirhangunec]

Also I can build with no errors on my M1 Macbook Pro runs on macOS sonoma 14

[Karyum]

@mohaahadji I also had the same issue, until I noticed today Vercel has a new Node version currently in beta test (20.x).
That fixed the issue for me, hope it helps

[jkingstoncsecond]

@Karyum do we need to change any settings in our vercel project or can we just enable it in the engines section of our packages.json?

[mohaahadji]

@Karyum just updated it and it works fine! Thanks for update.

[dataconcept-it]

@Karyum This works, thanks for the heads-up. It is finally resolved everyone! Very happy.

Steps to fix:

1. Click on your project on Vercel
2. Click on tab Settings
3. Change the Node Version in section Node.js Version to 20.x
4. Rebuild manually or commit new code to your project to deploy

I tested it with nextjs 14x and all packages, including react-pdf, updated. And it works.

Very happy, thanks to everyone for keeping this issue alive and for resolving it.

[dataconcept-it]

@jkingstonc this is how to fix it.

[jkingstoncsecond]

thanks @dataconcept-it, i have just tried this however and vercel is complaining about 20.x.x not being supported. I have changed the version to 20.x.x in my project settings, re-deployed and am getting the following error below. I have then also specified the version in my package.json to see if that fixed it "engines": {"node": ">20.0.0"}, and same error. is anyone else having this issue?

Error: Found invalid Node.js Version: ">20.0.0". Please set "engines": { "node": "18.x" } in your package.json file to use Node.js 18.

EDIT: Fixed, for anyone who has previously tried to fix this by using the VERCEL_CLI_VERSION environment variable suggested in other threads, I have removed this and now can use node 20.x.x

[dataconcept-it]

Can you remove the entire entry "engines": {"node": ">20.0.0"}, from your package.json file? I do not have this and it works without issues. I would try the following steps:

1. On your local machine, make sure node v20x is installed
2. Remove "engines": {"node": ">20.0.0"}, from package.json
3. Remove node_modules (rm -rf node_modules)
4. Reinstall packages (yarn/npm)
5. Run next build and see if that works.

If all works well, redeploy to vercel and see what happens

[dataconcept-it]

Ah, you fixed it already!

[jkingstoncsecond]

yep all working now appreciate the help!

[abhinavtalentinc]

Hello @smaeda-ks ,

We are seeing that a few users are not facing this issue on using Node version 20 in Vercel. Can you please confirm if the fix also going to be applicable for version 18, so that we can plan the upgrade accordingly?