Hi everyone and happy Friday,
Today when I hit the update all button for around 8 dockers, after 5 I started getting the 429-response error indicating the rate limit was hit (Understanding Your Docker Hub Rate Limit | Docker). Very weird so I reached out to docker hub. They confirmed that my IP violated the rate limit. Anyone know why this happened? 5 containers seem very short of 100 in 6 hours 
How many layers do they have? Those all count, as I understand it.
Sidenote: Back when they started doing this, I noticed that their accounting is sometimes wildly inaccurate. Hasn’t happened to me in a long while, though.
Well,
I run a docker-mirror.
The docker-mirror is configured to login via my free docker hub account, that increases the limit.
My docker sandbox is then configured to use the mirror (via daemon.json)
Thats a cool idea. Do you know if TrueNAS is thinking about supporting this as a feature, so this additional layer isn’t needed for updating?
Yeah, I’m thinking this is the case. The person that emailed me back is pushing me hard to buy an account. I tried to explain to them that wouldn’t fix my problem.
It doesn’t really do that much for you, unless you’re hosting for multiple systems…
yeah, other than allowing you to have an authenticated session with docker hub. I’m judging the value of 100 vs 200 image pulls and the effort involved.
I am seeing the same problem here. Even updating just a single app takes a long time because of the docker rate limit. It seems Scale just does anonymous pulls and I suspect that since my ISP has a CgNAT my apparent IP address is shared by thousands of people.
How is this supposed to work?
I think it does do anonymous pulls, which is why the limit is lower. Even a free account logged in has a higher limit. It would be awesome if there was a way to log into your docker account to increase the rate limit.
Nonono like seriously wtf?
How does it count those 100?
I got 19 active apps where a lot of them are still not using docker yet.
Clicked on Update for 7 apps and then I get this:
History
Related Kubernetes Events
2024-08-18 08:44:41
Error: ImagePullBackOff
2024-08-18 08:44:41
Back-off pulling image "paperlessngx/paperless-ngx:2.11.4"
2024-08-18 08:44:11
Error: ErrImagePull
2024-08-18 08:44:11
Failed to pull image "paperlessngx/paperless-ngx:2.11.4": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/paperlessngx/paperless-ngx:2.11.4": failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/paperlessngx/paperless-ngx/manifests/sha256:f3f2021c2771de4c18fb16938dbc7b2e0bc73a32168c16ef3c6914e4a5875d66: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
2024-08-18 08:44:08
Pulling image "paperlessngx/paperless-ngx:2.11.4"
Does Truenas ping every Container every hour to check for an update and that counts as one of those 100 calls?