error: failed to solve: failed to compute cache key: failed to copy: invalid status response 416
See original GitHub issueBehaviour
Got an error while computing the cache key:
error: failed to solve: failed to compute cache key: failed to copy: invalid status response 416 The range specified is invalid for the current size of the resource. for https://vth0acprodeus2file0.blob.core.windows.net/1665cc709f9c430f88b363d79c2f9f6f/35da92eddf84ec1194f60050f276280d?sv=2019-07-07&sr=b&sig=tAOoxQlbhCkNGNswTquFfnmtVgq3VCAP4Icc0bdnvlg%3D&se=2022-02-08T15%3A07%3A22Z&sp=r&rscl=x-e2eid-d10f7757-becb4d8c-94279385-0bd5086d
[4181](https://github.com/dfinity/internet-identity/runs/5110353933?check_suite_focus=true#step:4:4181)
Error: buildx failed with: error: failed to solve: failed to compute cache key: failed to copy: invalid status response 416 The range specified is invalid for the current size of the resource. for https://vth0acprodeus2file0.blob.core.windows.net/1665cc709f9c430f88b363d79c2f9f6f/35da92eddf84ec1194f60050f276280d?sv=2019-07-07&sr=b&sig=tAOoxQlbhCkNGNswTquFfnmtVgq3VCAP4Icc0bdnvlg%3D&se=2022-02-08T15%3A07%3A22Z&sp=r&rscl=x-e2eid-d10f7757-becb4d8c-94279385-0bd5086d
This was transient and I’m not sure how to reproduce it. Here is the GitHub actions run: https://github.com/dfinity/internet-identity/runs/5110353933?check_suite_focus=true
I reckon that might be a buildx
issue more than a build-push-action
issue; happy to migrate the ticket if you confirm.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:10
- Comments:25 (6 by maintainers)
Top Results From Across the Web
Docker - failed to compute cache key: not found - runs fine in ...
Check your .dockerignore file. Possible it ignores needed files for copy command and you get failed to compute cache key error.
Read more >How to fix-Docker docker failed to compute cache key not found
The Docker failed to compute cache key error is result of docker buildcommand which is executed on a directory where the Dockefile is...
Read more >Docker Error Failed To Compute Cache Key: Solution
The Docker failed to compute cache key problem occurs when the docker buildcommand is called in a directory that does not contain the...
Read more >Dockerfile, getting "failed to compute cache key" in the build
I have run a build without a catch in order to build it again correctly. Sadly, I got the following error: > [stage-1...
Read more >How To Fix the HTTP 416 Error (4 Methods) - Kinsta
HTTP status codes are numbers that represent the statuses of particular requests. These messages help identify whether a request was ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Now I am unable to use either ADD or COPY in my Dockerfile so the build process fails. I am receiving the errors listed below:
I used Dockerfile file in the home folder or under another folder, nothing changed.
Also running into this, both locally and in github actions