Docker builds failing
I see I now have two actors with builds failing in the same way every time. One has literally no changes since the last successful build 12h ago. The other had a few minor changes, all since reverted. Both pass all Dockerfile steps, but fail at:
ACTOR: Pushing Docker image to repository.
ACTOR: Error: Docker image build failed: NotFound: content digest sha256:.........
Is there a known issue?
Solution:Jump to solution
Switching to a different image in my Dockerfile seems to allow the build to work again
9 Replies
@hmcguirk just advanced to level 1! Thanks for your contributions! 🎉
Surely I'm not the only one experiencing this? Anyone else? Has been going on now for me for several hours, and my support chat escalated to a human has not been acknowledged by a human yet after an hour 😞
I'm completely blocked by this issue. For the last full day, I have been unable to build anything for either of my two actors, even though there are no changes to my code or config, and all Dockerfile stages pass successfully. Since Ive yet to hear from any human, I've spent all day trying 1) new actors linked to the same GitHub repository, 2) new actors linked to new repository with a copy of the same code, 3) new actor with new JS code, 4) inconsequential changes to the Dockerfile to force docker cache bypass, etc but I still have not found a way to unblock my work. The only possible solution I can find while searching online for the error
ACTOR: Error: Docker image build failed: NotFound: content digest sha256:59...... is perhaps to do a docker build --no-cache command, but I believe only apify engineers could do that??? I am currently unable to develop my Apify actors.Hi, if you run
docker build ... locally on your machine, it works correctly?Hi, yes, it works locally. I just tried another build there on Apify, and it failed in the same way
Can you share with me your actor id, or your user id?
Just FYI, I asked the question in the other thread as well.
Hi, I sent you the actor ID. The two issues are with the same actor. FYI, I've identified the specific container image that is causing the same build issue in all actors that use it. I believe it is the caching of this specific image: mcr.microsoft.com/dotnet/runtime:9.0 sha256:c4093cabaece5ace4a1c8fd240fa821b99a91c477c7b7dfe1dbf4678d09c57c4 https://mcr.microsoft.com/en-us/artifact/mar/dotnet/runtime/tags
Microsoft Artifact Registry
Microsoft Artifact Registry (also known as Microsoft Container Registry or MCR) Discovery Portal
Solution
Switching to a different image in my Dockerfile seems to allow the build to work again
I suppose it is missing or corrupted or something like that in Apify's Docker cache. Just a guess...
Builds on the platform are failing I’m experiencing the same issue. Did you recently make any changes to Apify’s internal code?