Apify

Apify Discord Mirror

Updated 5 months ago

Timeout When Pulling Docker Image

At a glance

The community member is experiencing timeouts while pulling a Docker image for their custom Actor. They are seeking solutions to prevent these timeouts, and also inquiring if it's possible to restart the Actor when this issue occurs, as the "Restart on error" setting does not seem to apply in this case since the Actor never gets started. The community member provides details about the Actor, including its name, origin, container size, and base Docker image, as well as the error message they are receiving.

eexu005
·
We've been noticing an uptick in the number of timeouts while pulling an Actor's Docker image. Can someone recommend any solutions on how to prevent this? Alternatively, is it possible to restart the actor under this scenario? The "Restart on error" Actor setting does not seem to apply, since the Actor never gets started in the first place. Any help is much appreciated!

Details:
Plain Text
Actor Name: Custom Actor
Origin: API (from 35.171.47.89 / ApifyClient/1.6.4 (linux; Python/3.11.9); isAtHome/True)
Container Size: 304.7 MB
Base Docker Image: apify/actor-python:3.11
Error Message: The Actor timed out. You can resurrect it with more timeout to continue where you left off.
Attachment
Screenshot_2024-05-28_at_10.31.11_AM.png
Add a reply
Sign up and join the conversation on Discord