Closed t-pohl closed 1 year ago
Hi @t-pohl ,
Does WUD use pulls to perform its checks such that the limit is hit and if yes can you throttle it?
WUD doesn't perform pull actions but it performs API calls which are counted from the quota.
To get around the Docker hub rate limits, you can use/combine the following 4 techniques:
Slow down the watch frequency (WUD_WATCHER_{watcher_name}_CRON
) ; please find the documentation here
Create a free Docker Hub account to increase the quotas ; please find the documentation here
Use immutable semver
tags instead of mutable tags for your containers because the watch process
involves lots more API calls when image digests
must be analyzed as mentioned in the doc here
Use images from alternate registries when possible (the Github Container Registry for instance)
Thank you so much!
Hey everybody,
has anybody experienced rate limits from Docker Hub while using WUD? According to the documentation of Docker Hub "pull rates limits are based on individual IP address. For anonymous users, the rate limit is set to 100 pulls per 6 hours per IP address. For authenticated users, it is 200 pulls per 6 hour period." This should definitely be sufficient for me and always was in the past but since I run WUD (without auto updates, ~20 containers which are watched) I frequently experience rate limits:
Error response from daemon: toomanyrequests: You have reached your pull rate limit.
Does WUD use pulls to perform its checks such that the limit is hit and if yes can you throttle it?