2 years ago
hey! all of a sudden my builds started failing with no code changes, just adding more replicas. any idea what i should look into?
12 ERROR: process "/bin/bash -ol pipefail -c npm install -g corepack@0.24.1 && corepack enable" did not complete successfully: exit code: 1
[stage-0 8/13] RUN --mount=type=cache,id=s/125d95ec-a5f3-4862-b2e2-d70b94e3c79e-/usr/local/share/cache/yarn/v6,target=/usr/local/share/.cache/yarn/v6 npm install -g corepack@0.24.1 && corepack enable:
0.386 /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)
0 Replies
2 years ago
yes there is, but first can you send the logs of the first build that failed, and the logs of the last build that worked?
how can i set the version, i have to run out for the day so want to try if i can
actually nvm we were getting a lot of traffic but looks like we're fine for now
2 years ago
yeah a failed build isnt going to affect the previous working deploy, but you would add a railway.json to your project with the version specified in it -
{
"$schema": "https://railway.app/railway.schema.json",
"build": {
"nixpacksVersion": "1.21.2",
"builder": "NIXPACKS"
}
}