Use HEAD requests to avoid being rate limited by DockerHub #631
-
Based on how exactly manifest requests will be counted, how many containers are monitored and which interval is configured this will probably affect many watchtower users. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 6 replies
-
Maybe we need to rethink about the skopeo solution @simskij @piksel |
Beta Was this translation helpful? Give feedback.
-
I've tried to answer this in more detail in #668 (comment), but the executive summary is that we don't need to change anything, the docker client will take care of this for us and make sure requests counting towards the rate limit only happens when the image digest has changed. 🎉 |
Beta Was this translation helpful? Give feedback.
-
Since this went live today, I am seeing the rate limit errors appearing frequently. I have 16 containers that I run on a home server, and most of the images I run don't even update every 24 hours. But starting at about 12pm EST I am getting the following error:
I am going to try to change the frequency to 60 minutes, so that I can stay under the rate limit (16 images * 6 pulls per period = 96 every 6 hours) But is there anything else I should be doing? I am looking into making authenticated calls, which would let me go to every 30 minutes. |
Beta Was this translation helpful? Give feedback.
-
Despite the pull rate limit message. Watchtower in my computer mangage to update the exactly image by polling every 30 seconds. |
Beta Was this translation helpful? Give feedback.
-
We've moved discussions on this topic to #669. Locking this discussion to make sure everything is available at the same place. |
Beta Was this translation helpful? Give feedback.
I've tried to answer this in more detail in #668 (comment), but the executive summary is that we don't need to change anything, the docker client will take care of this for us and make sure requests counting towards the rate limit only happens when the image digest has changed. 🎉