build-push-action: error: failed to solve: failed to compute cache key: failed to copy: invalid status response 416

Behaviour

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.

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 14
Comments: 29 (7 by maintainers)

Commits related to this issue

Remove buildx due to https://github.com/docker/build-push-action/issues/558 — committed to aviggiano/hack by aviggiano 2 years ago
as per this: https://github.com/docker/build-push-action/issues/558 — committed to nismod/infra-risk-vis by invalid-email-address 2 years ago
as per this: https://github.com/docker/build-push-action/issues/558 (#98) Co-authored-by: Chris N <you@example.com> — committed to nismod/infra-risk-vis by nicholac 2 years ago
as per this: https://github.com/docker/build-push-action/issues/558#issuecomment-1243765090 — committed to nismod/infra-risk-vis by invalid-email-address 2 years ago
as per this: https://github.com/docker/build-push-action/issues/558#issuecomment-1243765090 (#99) Co-authored-by: Chris N <you@example.com> — committed to nismod/infra-risk-vis by nicholac 2 years ago
as per this: https://github.com/docker/build-push-action/issues/558#issuecomment-1243765090 — committed to nismod/infra-risk-vis by invalid-email-address 2 years ago
as per this: https://github.com/docker/build-push-action/issues/558#issuecomment-1243765090 (#100) Co-authored-by: Chris N <you@example.com> — committed to nismod/infra-risk-vis by nicholac 2 years ago
as per this: https://github.com/docker/build-push-action/issues/558#issuecomment-1243765090 — committed to nismod/infra-risk-vis by invalid-email-address 2 years ago
as per this: https://github.com/docker/build-push-action/issues/558#issuecomment-1243765090 — committed to nismod/infra-risk-vis by invalid-email-address 2 years ago
as per this: https://github.com/docker/build-push-action/issues/558#issuecomment-1243765090 (#101) Co-authored-by: Chris N <you@example.com> — committed to nismod/infra-risk-vis by nicholac 2 years ago
as per this: https://github.com/docker/build-push-action/issues/558 (#98) Co-authored-by: Chris N <you@example.com> — committed to nismod/irv-frontend by nicholac 2 years ago
as per this: https://github.com/docker/build-push-action/issues/558#issuecomment-1243765090 (#99) Co-authored-by: Chris N <you@example.com> — committed to nismod/irv-frontend by nicholac 2 years ago
as per this: https://github.com/docker/build-push-action/issues/558#issuecomment-1243765090 (#100) Co-authored-by: Chris N <you@example.com> — committed to nismod/irv-frontend by nicholac 2 years ago
as per this: https://github.com/docker/build-push-action/issues/558#issuecomment-1243765090 (#101) Co-authored-by: Chris N <you@example.com> — committed to nismod/irv-frontend by nicholac 2 years ago
Trying to fix https://github.com/docker/build-push-action/issues/558 — committed to OctopusSolutionsEngineering/Octopub by mcasperson 9 months ago

Most upvoted 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:

ERROR: failed to calculate checksum of ref 1gjng5kin5uk6yv60uy8tx1hs::w6ujc2j2e2mnienr66n7godbb: failed to walk /tmp/buildkit-mount296995550/tmp: lstat /tmp/buildkit-mount296995550/tmp: no such file or directory

error: failed to solve: failed to compute cache key: failed to calculate checksum of ref 1gjng5kin5uk6yv60uy8tx1hs::w6ujc2j2e2mnienr66n7godbb: failed to walk /tmp/buildkit-mount296995550/tmp: lstat /tmp/buildkit-mount296995550/tmp: no such file or directory
Error: buildx failed with: error: failed to solve: failed to compute cache key: failed to calculate checksum of ref 1gjng5kin5uk6yv60uy8tx1hs::w6ujc2j2e2mnienr66n7godbb: failed to walk /tmp/buildkit-mount296995550/tmp: lstat /tmp/buildkit-mount296995550/tmp: no such file or directory

I used Dockerfile file in the home folder or under another folder, nothing changed.

+11

mmdeniz on Oct 24, 2022

Also running into this, both locally and in github actions

cyrus-za on Jun 30, 2022

I just got this error tonight. If anyone stumbles across this in the future, adding DOCKER_BUILDKIT=0 before the build command worked for me.

mattparlane on Mar 20, 2023

@crazy-max will do thanks!

nmattia on Oct 24, 2022

I’m also facing this issue across multiple projects 😞 this is the setup we’re using

      - uses: docker/build-push-action@v2
        with:
          context: .
          push: true
          tags: ghcr.io/org/repo:tag
          cache-from: type=gha
          cache-to: type=gha,mode=max

patrikholcak on Apr 25, 2022

@nmattia BuildKit 0.10.1 which is the latest stable so it should be the one used in your workflow if you have not enforced a specific BuildKit image in setup-buildx-action.

crazy-max on Apr 27, 2022

We updated the error message for this case in v0.10.1 with extra info. If you have received this error after that then please post the message here.

tonistiigi on Apr 26, 2022