aciku•4w ago

Have there been any recent changes to

Have there been any recent changes to Apify’s internal code? None of my builds are working now they all fail with: ACTOR: Error: Docker image build failed: NotFound: content digest sha256:59e226678…

13 Replies

acikuOP•4w ago

I’m 99% sure this issue is on Apify’s side. It seems like: • The image is built correctly (verified in the logs) • The failure happens only at the push step • The digest being used is either stale, misreferenced, or internally corrupted Could there be a problem with: • Apify’s internal Docker registry or CDN? • Digest caching/mapping in your build system? • Synchronization with Amazon ECR (if that’s what you use)?

hmcguirk•4w ago

Are you using the same dotnet container images in your Dockerfile, as I referenced in my threads above? I unblocked my builds by switching to a different image

acikuOP•4w ago

No matter which language I use even a simple Hello World actor in Python or other languages I keep getting the same error when pushing to Apify: ACTOR: Error: Docker image build failed: NotFound: content digest sha256:59e226... not found. It happens with all builds, even when using different base images like Rust, Python, etc. It seems like an internal issue with Apify’s Docker image caching or registry.

acikuOP•4w ago

acikuOP•4w ago

@Lukas Krivka Hey, help me out man I’ve been dealing with this error for several days now. 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.

Lukas Krivka•4w ago

I will report it, it is really weird that we didn't hear this from anyone else, maybe you have some specific setup that got corrupted send me yout build ID pls

acikuOP•4w ago

Everything was working fine 2 or 3 days ago, but now any actor I create and try to upload breaks — it doesn’t matter if it’s Python, Rust, JavaScript, or anything else.

acikuOP•4w ago

@Lukas Krivka Look, I made this video using an actor that only prints “Hello World” and even that doesn’t work! I did it this way on purpose, just to show that the issue isn’t on my side, but with the platform itself.

MEE6•4w ago

@aciku just advanced to level 5! Thanks for your contributions! 🎉

acikuOP•4w ago

I noticed something strange all the builds are failing with the same SHA, even though they’re completely different actors and builds: 2025-08-07T21:02:51.320Z ACTOR: Error: Docker image build failed: NotFound: content digest sha256:59e22667830bf04fb35e15ed9c70023e9d121719bb87f0db7f3159ee7c7e0b8d: not found

hmcguirk•4w ago

Yes, I noticed that for my failed builds too.

acikuOP•4w ago

It only works for me with this base image: apify/actor-node-basic. None of these work: node:18-slim, debian:bookworm-slim, python:3.11-slim, etc. It looks like I found the problem all images based on Debian (debian:bookworm-slim) are failing! That includes:

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.

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.

Lukas Krivka•4w ago

Can you send me a build ID pls? I tried to look at your account but don't see failed builds there So the team is already working on this

Have there been any recent changes to

Did you find this page helpful?