Railway•10mo ago

building got a error, but It was ok before...

#11 [stage-0 7/11] RUN --mount=type=cache,id=s/6195fab7-3631-4239-bd50-6ededa78afb2-/root/local/share/pnpm/store/v3,target=/root/.local/share/pnpm/store/v3 pnpm i --frozen-lockfile #11 0.481 Internal Error: ENOENT: no such file or directory, open '/root/.cache/node/corepack/lastKnownGood.json' #11 0.481 Error: ENOENT: no such file or directory, open '/root/.cache/node/corepack/lastKnownGood.json' #11 ERROR: process "/bin/bash -ol pipefail -c pnpm i --frozen-lockfile" did not complete successfully: exit code: 1 -----

[stage-0 7/11] RUN --mount=type=cache,id=s/6195fab7-3631-4239-bd50-6ededa78afb2-/root/local/share/pnpm/store/v3,target=/root/.local/share/pnpm/store/v3 pnpm i --frozen-lockfile:

0.481 Internal Error: ENOENT: no such file or directory, open '/root/.cache/node/corepack/lastKnownGood.json' 0.481 Error: ENOENT: no such file or directory, open '/root/.cache/node/corepack/lastKnownGood.json' ----- Dockerfile:21 ------------------- 19 | COPY . /app/. 20 | RUN --mount=type=cache,id=s/6195fab7-3631-4239-bd50-6ededa78afb2-/root/local/share/pnpm/store/v3,target=/root/.local/share/pnpm/store/v3 npm install -g corepack && corepack enable 21 | >>> RUN --mount=type=cache,id=s/6195fab7-3631-4239-bd50-6ededa78afb2-/root/local/share/pnpm/store/v3,target=/root/.local/share/pnpm/store/v3 pnpm i --frozen-lockfile 22 | 23 | # build phase ------------------- ERROR: failed to solve: process "/bin/bash -ol pipefail -c pnpm i --frozen-lockfile" did not complete successfully: exit code: 1 Error: Docker build failed

Solution:

Nixpacks uses something known as Corepack internally, corepack recently pushed a bad that's causing issues in Railway's build process, and since nixpacks always uses the latest version- it's using that bad version by default. For now, here's a workaround; add a nixpacks.toml file in your app with the following content: ```toml...

Jump to solution

19 Replies

Percy•10mo ago

Project ID:

6195fab7-3631-4239-bd50-6ededa78afb2,6195fab7-3631-4239-bd50-6ededa78afb2,6195fab7-3631-4239-bd50-6ededa78afb2,6195fab7-3631-4239-bd50-6ededa78afb2

Solution

Fragly•10mo ago

[phases.install]
cmds = ["npm install -g [email protected] && corepack enable", "yarn install --check-cache"] 
dependsOn = ["setup"]

[phases.install]
cmds = ["npm install -g [email protected] && corepack enable", "yarn install --check-cache"] 
dependsOn = ["setup"]

AZ263OP•10mo ago

why Unsupported engine?

Brody•10mo ago

set engines.node to 20 in your package.json

AZ263OP•10mo ago

add nixpacks.toml, but still got this

AZ263OP•10mo ago

Brody•10mo ago

it's also still on node 21, please show us how/where you have added the nixpacks.toml and set the engine version

AZ263OP•10mo ago

its turbo project, add nixpacks.toml to apps/project

Brody•10mo ago

what version do you use locally

AZ263OP•10mo ago

v16.16.0

Brody•10mo ago

then please set it to just 16.16.0 as for the nixpacks.toml, does your service deploy from the root of the repo?

dennisthetennis_•10mo ago

after replace it still have different error log

Brody•10mo ago

~~do you think you could open your own help thread please?~~

AZ263OP•10mo ago

He's my colleague

Brody•10mo ago

oh my bad in that case, could you send the build logs with this? https://bookmarklets.up.railway.app/log-downloader/

dennisthetennis_•10mo ago

after move the toml file to root dir the issue is solved, thanks everyone :salute:

Brody•10mo ago

yeah i figured, happy you solved this!

Gaming

Programming

building got a error, but It was ok before...