-
Notifications
You must be signed in to change notification settings - Fork 580
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: failed to calculate checksum of ref ... no such file or directory #910
Comments
https://github.com/theAkito/docker-murmur/actions/runs/5627573725/job/15250407075#step:7:6824
It looks similar to docker/buildx#1899. Do you repro locally with:
|
Locally, I'm getting the following.
|
Ok can you change this step to enable BuildKit container logs: - name: Set up Docker BuildX
uses: docker/setup-buildx-action@v2
with:
buildkitd-flags: --debug That could be useful to us. |
After debugging the issue locally, I came to the conclusion that it was a mistake in the configuration of the Dockerfile, where a file was there before, but in a new version of the deployed app it's not there, anymore. Hence, "no such file or directory". However, I must emphasise, that the error is very unintuitive & should be more clear. Is this something that would be reported on moby or where would that be accomplished? As for this specific issue at hand, it can be considered resolved for all I expected. |
We have made some enhancements related to this such as moby/buildkit#3990 Just of curiosity, could you try with latest 0.12.0 of BuildKit?: - name: Set up Docker BuildX
uses: docker/setup-buildx-action@v2
with:
driver-opts: |
image=moby/buildkit:v0.12.0
buildkitd-flags: --debug |
Downgrade docker on windows helps to me |
Behaviour
Catching up on #558 (comment).
Steps to reproduce this issue
https://github.com/theAkito/docker-murmur/blob/master/.github/workflows/docker-build-push-app-buster-slim.yml
Expected behaviour
Process should complete successfully.
Actual behaviour
Internal Docker processing does not complete successfully, leading to failed Docker builds.
Configuration
Logs
logs_9.zip
Additional Context
dotnet/dotnet-docker#4716
The text was updated successfully, but these errors were encountered: