You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.2Feb 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 therailway 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:
The text was updated successfully, but these errors were encountered: