a month ago
This has been happening for a while. I have a node application deployed using railpack which crashes repeatedly on deployment with the following error.
node: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory
Any assistance would be appreciated.
6 Replies
a month ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
19 days ago
I had the same problem but with bun, and the fix for me was prefixing the build and start scripts in my package.json (which I specify as cmds in railway.toml) with bun --bun , now it looks like this
"build": "bun --bun next build --turbopack",
"start": "bun --bun next start",It seems to be a problem with node because with Railpack 0.11 I was seeing bun as the runtime in my deployment, while with 0.12 I see both bun and node. After the fix I had it still shows both of them but it just deploys and works fine.
yaziciahmet
I had the same problem but with bun, and the fix for me was prefixing the build and start scripts in my package.json (which I specify as cmds in railway.toml) with bun --bun , now it looks like this"build": "bun --bun next build --turbopack", "start": "bun --bun next start",It seems to be a problem with node because with Railpack 0.11 I was seeing bun as the runtime in my deployment, while with 0.12 I see both bun and node. After the fix I had it still shows both of them but it just deploys and works fine.
19 days ago
Hi! Do you have a Dockerfile for this?
b-sherqoziyev
Hi! Do you have a Dockerfile for this?
18 days ago
I don't use Dockerfile, I use Railpack directly.
18 days ago
I tried to see if this was possible with node but --node is an invalid option.
17 days ago
I'm not sure what fixed it, but I updated one of my packages today and the deployment was successful without crashing.
Status changed to Solved hifo • 17 days ago