I’m experiencing an issue where all my builds succeed, but fail at the push step with the following
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.
8 Replies
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!
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
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
@aciku 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.
It looks like I found the problem all images based on Debian (debian:bookworm-slim) are failing! That includes:
Hi @aciku, does this issue still prevail?
Yes, the issue is still present.
Our developers are aware of this issue, but it is unfortunately a tricky one :/
Currently, there is no ETA, sorry 🙏