You can bypass the corrupted build cache by adding the environment variable NO_CACHE=1 to your service, which forces a fresh build without any cached layers. Once the build succeeds, you can remove that variable to re-enable caching going forward.

The automated solution did not work. NO_CACHE=1 was applied but the

build still fails with the same error:

"cannot copy to non-directory: /var/lib/buildkit/runc-overlayfs/

cachemounts/buildkit.../app/node_modules/.pnpm/

@anthropic-ai+sdk@0.30.1/node_modules/@types/node"

This reproduces across Nixpacks and Railpack builders, with and

without NO_CACHE=1, across 8+ deployments. The BuildKit cache mount

for this service appears permanently corrupted. Manual intervention

required to clear it.

Service: c1245d2f-c901-40eb-b6f6-7ec696af0ab8

We've rolled the caches and upgraded buildkit. Does this issue persist still? If so we will escalate it to the builds team

Hi Jake,

Just wanted to let you know the issue is now resolved — the build is

deploying successfully. The root cause was node_modules being committed

to the repository, which caused the conflict with Railpack's symlink

structure.

Sorry for the back and forth, and thank you for rolling the caches and

escalating so quickly. Really appreciate the support!