Puppeteer: Failed to launch the browser process - `GLIBC_2.36' not found.
Hi!
I'm using puppeteer to take a screenshot of a website being hosted on the railway service itself but everytime i get to the code i get the following error:
I'm using node js.
I've added the following to the nixpacks.toml from the puppeteer troubleshooting doc but keep running into the same
https://pptr.dev/troubleshooting#chrome-doesnt-launch-on-linux
project id: a8a105b0-b1ab-4a67-9304-89816de88393
Troubleshooting | Puppeteer
Chromium currently does not provide arm64 binaries for Linux. There are only
Solution:Jump to solution
This worked for me at least in getting rid of the shared lib dependency issue
```
FROM node:20.9.0
...
13 Replies
Project ID:
a8a105b0-b1ab-4a67-9304-89816de88393
the nixpacks.toml
might be best to switch to a Dockerfile based build for this, a similar user just had this issue https://discord.com/channels/713503345364697088/1210022480832372766/1210037069594890280
I see, should i use a similar template you've posted at the end there ? i'm not too experienced with dockerfiles.
similar, yes
im assuing your start command would need to change, aka the last line of that dockerfile
trying this
why
npm install
instead of npm ci
?
you have also omitted the environment variablesah good spot - i was creating it from scratch and forgot those, didn't know about ci - trying updated
Solution
This worked for me at least in getting rid of the shared lib dependency issue
awsome, glad you where able to solve
Actually, i had to redo the dockerfile since it would create the image but it would fail at runtime - the following works end to end
with the following launch options for puppeteer
We are randomly getting the same issue now too. I assume there has been some update to nixpacks thats caused it
yeah, you have assumed correctly, it's unfortunate, but the dockerfile they provided is a good starting point for you, and it's going to be far less likely to randomly break