You can, but only 10 images per hour. You’d be doing some wild shit to go over those 10 per hour.
nekusoul@lemmy.nekusoul.de
on 21 Feb 18:32
nextcollapse
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.
superglue@lemmy.dbzer0.com
on 21 Feb 22:44
collapse
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.
threaded - newest
For those already authenticated and wondering how many pulls they use, you can check your usage here:
hub.docker.com/usage/pulls
Start uploading to either ghcr.io (github) or quay.io (redhat)
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.
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.