Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't deploy on PaaS: Error loading shared library ld-linux-x86-64.so.2 #2516

Open
httpiga opened this issue Feb 17, 2025 · 1 comment
Open

Comments

@httpiga
Copy link

httpiga commented Feb 17, 2025

Describe the bug
While deploying the server to Railway as instructed in Wasp docs, I get the error Error loading shared library ld-linux-x86-64.so.2: No such file or directory (needed by /app/node_modules/onnxruntime-node/bin/napi-v3/linux/x64//libonnxruntime.so.1.14.0) after running the railway up command.
The failure happens when the build process executes the line node --enable-source-maps -r dotenv/config bundle/server.js.
It happens because Alpine distro lacks glibc.
I fixed by updating the generated Dockerfile to use Debian instead of Alpine:

FROM node:18.18.0 AS node
...
FROM node AS base
RUN apt-get update && apt-get upgrade -y
...
RUN apt-get install -y python3 build-essential libtool autoconf automake
...
Removed 
# In case they want to use python3 in their app.
as the base image already includes necessary packages.
@httpiga httpiga changed the title Can't deploy to Railway: Error loading shared library ld-linux-x86-64.so.2 Can't deploy on PaaS: Error loading shared library ld-linux-x86-64.so.2 Feb 17, 2025
@sodic
Copy link
Contributor

sodic commented Feb 21, 2025

Thanks for the report @httpiga.

I remember we had issues with glibc before. @Martinsos knows more than I do about that so I'll leave this to him.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants