Build failure — cache key computation error on Metal builder ("/frontend": not found)
edouardwilssonn-sketch
HOBBYOP

16 days ago

Hello,

My service "frontend" in project signifex-shop fails to build consistently for the past hour, across 5+ consecutive attempts, with two different errors depending on the attempt:

Most recent error (build ID ac253d6c, 2026-08-05 12:50 GMT+2):

Build Failed: build daemon returned an error < failed to solve: failed to compute cache key: failed to calculate checksum of ref nts0ru0lq536bnrt42bo9ft3k::s5gxfk588jwidfd4yelv7tuyb: "/frontend": not found >

This happens at the "COPY frontend/ ./" step of the Dockerfile, while previous steps using the same folder (COPY frontend/package.json...) are marked "cached" without issue. The frontend/ folder is definitely present in my GitHub repo (edouardwilssonn-sketch/signifex-shop, main branch) — I've verified this.

Earlier attempts failed with a different error:

container process is already dead / context canceled

also at the very first Dockerfile command, on a Dockerfile that worked fine for the previous 5 deployments.

Builder involved: builder-wvldab (Metal builder), US West / sfo region.

Could you check if there's a known issue with build cache or the Metal builder infrastructure right now? An option to force a build without cache would also help in the meantime.

Thank you,

Solved

1 Replies

Railway
BOT

16 days ago

Your service is configured to use the Railpack builder with a root directory of frontend, not a Dockerfile, so the COPY frontend/ ./ step you are describing would not apply to this service's actual build pipeline. If you intend to use a Dockerfile, you can switch the builder in the service's settings. To force a build without cache, add the environment variable NO_CACHE=1 to the service and redeploy.


Status changed to Awaiting User Response Railway 16 days ago


Railway
BOT

9 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 9 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...