lucaslorentz
Consider making the image available on an alternative registry
Docker Hub is about to implement new usage limits of 10 pulls per IP per hour on anonymous users. (See https://docs.docker.com/docker-hub/usage/) Consider offering the image on an additional registry like the GitHub container registry to help users who may run up against this usage limit.
I'm currently in the process of switching to other registries for every container image I run that offers them and noticed this one doesn't.
Thank you for the awesome project. It makes spinning up new services so much easier for me!
How are you even making that many pulls per hour? You should only be triggering a pull when the image updates, which is quite infrequent.
@francislavoie On a typical day, I'm not, but I think a better question is why would I want to be limited to 10 pulls per hour? I can give many scenarios where I wouldn't, but I can't think of a time I would. This is not the only container I run. I run about 60 different containers, so if I decide to pull updates for all of them and if all of them do have updates to pull, that's 6 hours of my time, mostly of waiting around for the limit to reset each hour. Why would I want this when the images could just be hosted on a different registry that has a less strict rate limit? What if my device dies and I have to bring all of my stacks up again from scratch on a new device. Should that take 6 hours, or would it be preferable to not be under that rate limit? What if I'm in a country that decides Docker Hub is a threat and blocks it, leaving me no way to access except behind a VPN. Now, I'm sharing 10 pulls per hour with everyone else who happens to connect through the same VPN server as me. Someone smarter than me can probably come up with a half dozen other scenarios in which this is not ideal.
If this were the only container I was running, I agree it would probably be difficult to get to 10 pulls per hour (except maybe under the VPN scenario), but this particular image wouldn't be very useful then — if I didn't want to be able to configure other services in Caddy via Docker labels, I'd just run a plain Caddy image. Given that I am running services behind it and each of those has one or more images associated with it, I can think of several scenarios where this rate limit could be very inconvenient.
Just considered that maybe one of us is misinterpreting the rate limit. Are you thinking that it's 10 pulls per image per hour? I assumed they meant globally 10 pulls across all images per IP per hour. I'm not 100% certain who is right, but I don't see language to suggest the limit is per image which leads me to believe it is global. Happy to be wrong though.
How are you even making that many pulls per hour? You should only be triggering a pull when the image updates, which is quite infrequent.
Yeah, @raddevon is correct. It is very easy to go over Docker Hubs rate limits especially if you run a lot of services.
It looks like they've since dialed back the rate limiting so it's not nearly as bad, but it's still a valid cause for concern.
