- cross-posted to:
- selfhosted@lemmy.world
- cross-posted to:
- selfhosted@lemmy.world
You must log in or register to comment.
For those already authenticated and wondering how many pulls they use, you can check your usage here:
Use podman and quay.io
This will probably hit downstream users who don’t even know (or care) what service the application they use is hosted on.
So you can’t deploy without auth?
You can, but only 10 images per hour. You’d be doing some wild shit to go over those 10 per hour.
I just run some self hosted servers. I most definitely run more than ten services, not few of the consisting of multiple containers. With this change I’d basically hit the limit every time I do maintenance and pull the latest versions of all the images I run.
I mean imagine migrating to a new server. One of my server has like 30 containers. Now my outage is 3 hours instead of 45 mins.
I’m not complaining, however. It is a free service they are providing.
Yeah looking back, this isn’t my best take probably. As you say though, it is a free service.
I don’t think it’s that wild. Arr suite + jellyfin, jellyseer & qbittorrent already are 7.
Then apps like immich are 4 individual images (2 probably frozen forever, but still)
If I pull all my services, it’s going to be around 15 now. And I use Mullvad VPN, so I’m sharing my IP with thousands of people.
Also, this will be an issue for those in a dorm or work, or similar shared connection (CGNat too?), even if trying to pull only one.
So how big is the chance you’re pulling your whole stack at once and not deploying service by service to check if it’s even working properly on the new deployment?
99%
Immich and it’s dependencies are the only ones that I investigate a bit before pulling, so they are their own compose. Everything else goes at the same time.
Once immich goes stable, even it will be pulled with the rest.
This is one option to help with that for images not on other registries: https://cloud.google.com/artifact-registry/docs/pull-cached-dockerhub-images
