Builds failing with: PHASE_SETUP Structure needs cleaning (os error 117)
Anonymous
PROOP

15 days ago

Project ID: 8cce23fc-b690-4e9e-a11d-1f2a3e78db78

Service ID: 76c95a1f-b363-42df-8ebb-96649e32a7d4

Environment ID: 9aec7ce1-ada2-40a5-aa6f-94142067db55

Deployment ID: 8a54c163-ed70-419b-a0be-f806bd9fe198

Description:

All of our builds are failing with below error message not related to our code. Any help appreciated.

Error:

phase PHASE_SETUP failed (exit 1): clear dest before re-clone: Structure needs cleaning (os error 117)

Awaiting User Response

3 Replies

Status changed to Awaiting Railway Response Railway 15 days ago


Anonymous
PROOP

15 days ago

We tried turning off Express build, however then it falls back to Nixpacks, where we get this error:


2026-08-06T17:56:43.141420407Z [inf]  npm warn deprecated tsconfck@3.1.6: unmaintained

2026-08-06T17:56:44.895338614Z [inf]  

added 553 packages, and audited 554 packages in 4s

203 packages are looking for funding

2026-08-06T17:56:44.895373396Z [inf]    run `npm fund` for details

2026-08-06T17:56:44.918846095Z [inf]  

6 vulnerabilities (1 low, 2 moderate, 3 high)

To address issues that do not require attention, run:

  npm audit fix

To address all issues (including breaking changes), run:

  npm audit fix --force

Run `npm audit` for details.

2026-08-06T17:56:45.584816432Z [inf]  [stage-0  6/10] RUN --mount=type=cache,id=s/76c95a1f-b363-42df-8ebb-96649e32a7d4-/root/npm,target=/root/.npm npm ci

2026-08-06T17:56:45.620126601Z [inf]  [stage-0  7/10] COPY . /app/.

2026-08-06T17:56:45.999459630Z [err]  [stage-0  7/10] COPY . /app/.

2026-08-06T17:56:46.036310921Z [err]  Build Failed: build daemon returned an error < failed to solve: cannot replace to directory /var/lib/buildkit/runc-overlayfs/cachemounts/buildkit211985553/app/node_modules with file >

chandrika
EMPLOYEE

15 days ago

Hi there, we've escalated this to the team and are looking into fixing it


Status changed to Awaiting User Response Railway 15 days ago


chandrika
EMPLOYEE

15 days ago

The build environment for your service has been cleared. Please try deploying again - your builds should now complete successfully.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...