2 years ago
I've tried solutions such as this one where I have deleted json-lock.json
#12 [stage-0 8/13] RUN --mount=type=cache,id=s/84e6abc2-8d4a-4d50-9ac3-29a8372650c9-/root/npm,target=/root/.npm npm ci
#12 0.366 /nix/store/5scibl4zxs148k50bmi8bqyaqlxrsw02-nodejs-18.20.2/bin/node: /nix/store/xpxln7rqi3pq4m0xpnawhxb2gs0mn1s0-gcc-12.3.0-lib/lib/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /nix/store/5scibl4zxs148k50bmi8bqyaqlxrsw02-nodejs-18.20.2/bin/node)
#12 ERROR: process "/bin/bash -ol pipefail -c npm ci" did not complete successfully: exit code: 1
[stage-0 8/13] RUN --mount=type=cache,id=s/84e6abc2-8d4a-4d50-9ac3-29a8372650c9-/root/npm,target=/root/.npm npm ci:
0.366 /nix/store/5scibl4zxs148k50bmi8bqyaqlxrsw02-nodejs-18.20.2/bin/node: /nix/store/xpxln7rqi3pq4m0xpnawhxb2gs0mn1s0-gcc-12.3.0-lib/lib/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /nix/store/5scibl4zxs148k50bmi8bqyaqlxrsw02-nodejs-18.20.2/bin/node)
Dockerfile:25
23 | ENV NIXPACKS_PATH /app/node_modules/.bin:$NIXPACKS_PATH
24 | COPY . /app/.
25 | >>> RUN --mount=type=cache,id=s/84e6abc2-8d4a-4d50-9ac3-29a8372650c9-/root/npm,target=/root/.npm npm ci
26 |
27 | # python:install phase
ERROR: failed to solve: process "/bin/bash -ol pipefail -c npm ci" did not complete successfully: exit code: 1
Error: Docker build failed
ⓘ Deployment information is only viewable by project members and Railway employees.
6 Replies
2 years ago
For some more context I've only made some small updates to my repo and it will not deploy anymore. The last successful deployment was on May 14th.
I created a branch from the last working commit and even that will not deploy any more.
edit: typo
2 years ago
Have you found a solution to this:? I have ran into the same issue where with "`GLIBCXX_3.4.32' not found". I ran into this issue after my nodejs app had a dependency that required python for some reason. So I setup my nixpacks provider to include a python install and now I'm running into this issue.
2 years ago
No I do not. Do you have an example of one I could try or start from?
2 years ago
I think I fixed this by deleting my node modules folder and deleting the package-lock.json and the reinstalling
rm -rf node_modules/
rm package-lock.json
npm install
Status changed to Solved Railway • almost 2 years ago