-
Notifications
You must be signed in to change notification settings - Fork 441
-
Star 3.3k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] Error: failed to solve: rpc error: code = Unknown desc = content digest sha256:...: not found #101
[bug] Error: failed to solve: rpc error: code = Unknown desc = content digest sha256:...: not found #101
Comments
tonistiigi
commented
Jul 8, 2019
I think I see how this could happen if there are parallel builds that end up building the same image and one ends up finishing with this error during load. Is this case possible in your case? If not then I need to enable debug logs in buildx cause without them it's very hard to guess what actually happened. |
tonistiigi
commented
Jul 9, 2019
With #102 you can create the builder instance with |
shykes
commented
Jul 10, 2019
Yes, that is very likely. Both environments where the issue occurred match your description. In fact I am also encountering another issue (issue coming soon) which is definitely related to concurrency. |
shykes
commented
Jul 15, 2019
Thank you! |
kegi
commented
May 6, 2020
•
edited
edited
I think this should be reopen. I'm building for 3 platforms in parallel. Docker version : 19.03.8, build afacb8b |
MarkCarbonell98
commented
May 13, 2020
Same error here:
Using docker Docker version 19.03.8, build afacb8b7f0 On a Raspberry Pi with arm32v7 architecture |
skabashnyuk
commented
May 20, 2020
I'm building for 2 platforms in parallel. Got the same here https://github.com/eclipse/che-dashboard/actions |
tonistiigi
commented
May 20, 2020
Please open a new issue with reproduction steps if you think there is still a way to hit this. |
shaunc
commented
Jul 19, 2020
According to https://stackoverflow.com/questions/59868448/rpc-error-code-unknown-desc-failed-to-build-llb this is a resource issue. Indeed, adding another processor and a Gig seems to be working for me. Obviously a better error would be appropriate, at the least. |
holdenk
commented
Oct 3, 2020
Just ran into this as well, cross building locally with qemu the docker file was
and the setup file
My build command was: re-running seems to solve the issue though. |
huguesBouvier
commented
Feb 13, 2021
•
edited
edited
I am getting the same issue too: It happened for arm64 |
andrewthetechie
commented
Feb 13, 2021
Seeing this as well, building for amd64 and arm64 in parallel ` ocker versio2 | Client: Docker Engine - Community In my case, this is failing as a part of a drone build running inside a kubernetes cluster. |
tonistiigi
commented
Feb 13, 2021
This issue has been closed. If you are seeing something similar create a new issue with a reproducer and full version infos. |
lei-cheung
commented
Sep 15, 2021
use |
itspawanhere
commented
Feb 13, 2022
I have a Macbook pro with M1 chip. |
Amin-asadii
commented
Feb 21, 2022
ERROR [bass-master_ida stage-1 4/24] COPY ida.run /installation/ |
cah-iovani-juarezgarcia
commented
Apr 20, 2022
Having same error, im connecting from a different country from where i usually connect so... maybe a vpn related issue? |
yvess
commented
May 3, 2022
have the same error on Mac (docker desktop 4.7.1) only arm64 buildx with:
|
alberto56
commented
Nov 7, 2022
I get this error if I use the DigitalOcean "Docker" image, which has an old version of Docker on it. If I use the "Ubuntu" image and install Docker myself, I no longer get this error. |
digitaltim-de
commented
Dec 9, 2022
Having the same error randomly... |
sabaimran
commented
Feb 14, 2023
In case it might help someone else, I ran into the issue because my |
olahsymbo
commented
Feb 20, 2023
I solved this issue by first deleting |
crazy-max
commented
Jul 28, 2023
Locking this issue. Open a new issue with reproduction steps if you hit this again. Thanks. |
Summary
This error occurs randomly, and causes a build to fail when otherwise it would have succeeded. On re-running the exact same build, the error goes away.
Environment
docker-buildx version: standalone binary downloaded from https://github.com/docker/buildx/releases/download/v0.2.2/buildx-v0.2.2.linux-amd64 (sha256 5c31e171440213bb7fffd023611b1aaa7e0498162c54cb708c2a8abe3679717e)
Docker engine version:
How to reproduce
Unfortunately, I have not found a way to reproduce it reliably. However it does not seem to be related to the contents of the Dockerfile, since I have reproduced it (accidentally) with two completely unrelated Dockerfiles.
Based on my understanding of the error message, it appears that
--load
is required to reproduce.Here is the output of the most recent occurrence:
The text was updated successfully, but these errors were encountered: