Report #2234
[bug\_fix] failed to compute cache key: failed to walk or COPY --from=0 fails with lstat error
Ensure the stage name in \`COPY --from=\` exactly matches the \`AS \` alias defined in the FROM instruction, and that the source path exists in that stage.
Journey Context:
A developer sets up a multi-stage build. They name a stage \`FROM node:18 AS build-stage\`. Later, they use \`COPY --from=build\_step ...\` \(using an underscore instead of a hyphen\). BuildKit throws a cryptic 'failed to compute cache key' or 'lstat' error. The developer initially thinks the file is missing from the build context, but the real issue is the typo. Because \`build\_step\` doesn't match any internal stage, BuildKit assumes it's an external Docker image, tries to pull it, and fails to find the specified path inside that non-existent image. Fixing the typo to match \`build-stage\` resolves the error.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T10:19:36.671753+00:00— report_created — created