https://apify.com/ logo
Join Discord
Powered by
I’m experiencing an issue where all my builds succ...
# apify-platform
a
Copy code
ACTOR: Error: Docker image build failed: NotFound: content digest sha256:59e2266...: not found
This happens even with minimal “Hello World” actors in different languages (Python, Rust, etc.), and using different base images such as python:3.11, python:3.10, or even full-size variants. The image is clearly being built successfully (log shows Successfully built ...), and this error appears only when Apify tries to push the image to your internal Docker registry. https://cdn.discordapp.com/attachments/1402838418450288752/1402838418987417631/Screenshot_2025-08-06_at_9.18.49_PM.png?ex=68955e96&is=68940d16&hm=23eb4e1c00f63fca591879bc53ad47a6317bf8aa6552e2d3d70be53e90ad3b44&
a
message has been deleted
o
Hi! Your error is often caused by a corrupted or missing Docker layer in the cache, or a registry sync issue. A clean build might be a good idea, as it forces the platform to rebuild every layer from scratch, ignoring any potentially problematic cached layers. This often resolves digest and push errors like the one you are experiencing. To do so, start a clean built right from the UI. If the issue persists, let me know. Good luck! https://cdn.discordapp.com/attachments/1402838418450288752/1402881450159636541/image.png?ex=689586a9&is=68943529&hm=59da17f51919776aa96335c03bf8c5a83aa413e4d77502f7a92a2e10fb256183&
h
Is that clean build option new? I didn't notice it before, but perhaps I just wasn't looking there - I mean I would expect that option under the Actor's Builds tab
a
It doesn’t help, I’m still getting the same error.
I’ve already tried using the clean build option from the UI, created a new actor, and even changed the base image none of that worked. The issue clearly seems to be on your registry side.
@olexandra_59608
o
@acikuu We've raised your issue internally, as it seems like you're not alone in experiencing it. As soon as we get some new information, I'll get back to you.
a
It looks like I found the problem all images based on Debian (debian:bookworm-slim) are failing! That includes:
Copy code
1. node:18-slim  
2. node:20-slim  
3. node:lts-slim  
4. node:current-slim  
5. python:3.11-slim  
6. python:3.12-slim  
7. ruby:3.2-slim  
8. golang:1.21-slim  
9. golang:1.22-slim  
10. openjdk:17-slim  
11. openjdk:21-slim  
12. php:8.2-cli-slim  
13. php:8.3-cli-slim  
14. perl:5.36-slim  
15. mono:6.12-slim  
16. erlang:26-slim  
17. elixir:1.15-slim  
18. r-base:4.3.1  
19. rust:1.72-slim  
20. swift:5.9-slim  
21. nimlang/nim:latest-slim  
22. julia:1.9-slim  
23. crystal:1.9-slim  
24. dart:3.2-slim  
25. haskell:9.4-slim  
26. debian:bookworm-slim  
27. buildpack-deps:bookworm-slim  
28. gcc:13-slim  
29. clang:17-slim  
30. cmake:3.27-slim  
31. make:latest-slim  
32. git:2.42-slim  
33. docker:24.0-slim  
34. busybox:glibc-slim  
35. bash:5.2-slim  
36. curlimages/curl:slim  
37. wget:latest-slim  
38. yq:latest-slim  
39. helm:3.13-slim  
40. aws-cli:2.13-slim  
41. gcloud:latest-slim  
42. azure-cli:2.55.0-slim  
43. terraform:1.6-slim  
44. ansible:latest-slim  
45. kubectl:1.30-slim  
46. tensorflow/tensorflow:latest-py3  
47. tensorflow/tensorflow:2.15.0  
48. pytorch/pytorch:latest  
49. pytorch/pytorch:2.2.0  
50. jupyter/base-notebook  
and many other images based on Debian bookworm-slim.
a
Hi @acikuu, does this issue still prevail?
a
Yes, the issue is still present.
a
Our developers are aware of this issue, but it is unfortunately a tricky one :/ Currently, there is no ETA, sorry 🙏
PreviousNext
Powered by