publish on container registry without draconian rate limits #7557

New Issue

GiteaMirror · 2025-11-02T07:29:45-06:00

GiteaMirror commented

2025-11-02 07:29:45 -06:00

Originally created by @ibotty on GitHub (Jul 7, 2021).

Description

It would be great to publish the image on a registry that does not impose draconian usage limits. I like quay.io which has a free tier that is sufficient, but using github's registry would work as well.

Originally created by @ibotty on GitHub (Jul 7, 2021). ## Description It would be great to publish the image on a registry that does not impose draconian usage limits. I like quay.io which has a free tier that is sufficient, but using github's registry would work as well.

GiteaMirror added the type/proposal topic/distribution labels 2025-11-02 07:29:45 -06:00

GiteaMirror commented

2025-11-02 07:29:46 -06:00

@techknowlogick commented on GitHub (Jul 7, 2021):

As a general statement, instead of direct response to this proposal itself. There is a PR to include a docker registry into Gitea itself, so possible gitea.com would be an option when/if it gets merged, and when we migrate this repo there too.

In terms of this proposal, I'd be amenable to migrating elsewhere, however if we were to move rather than moving to another "free" option which could impose similar limits in the future, I'd prefer hosting ourselves as then we are less beholden to corporate overlords. Options available to us right now are: 1. sign up to Docker Hub's OSS program which does remove ratelimits for anon pulls (we looked at this last year, however it requires us to apply every year, write marketing content including blogs webinars etc.., and add some specific information to our website and documentation. We aren't opposed to that, but it just takes time away from building Gitea), and 2. host a registry ourselves (if gitea docker registry comes to fruition, then we could remap docker pulls without breaking URLs for users). With no. 2, we have infra already in place that we could do this with, and I personally have contributed code to docker's registry (now a CNCF project called distribution).

I should note, I am very thankful for docker hub providing bandwidth and storage for us for the past years, and while we now pay them, our cost to them is likely much higher than they recoup from us.

@techknowlogick commented on GitHub (Jul 7, 2021): As a general statement, instead of direct response to this proposal itself. There is a PR to include a docker registry into Gitea itself, so possible gitea.com would be an option when/if it gets merged, and when we migrate this repo there too. In terms of this proposal, I'd be amenable to migrating elsewhere, however if we were to move rather than moving to another "free" option which could impose similar limits in the future, I'd prefer hosting ourselves as then we are less beholden to corporate overlords. Options available to us right now are: 1. sign up to Docker Hub's OSS program which does remove ratelimits for anon pulls (we looked at this last year, however it requires us to apply every year, write marketing content including blogs webinars etc.., and add some specific information to our website and documentation. We aren't opposed to that, but it just takes time away from building Gitea), and 2. host a registry ourselves (if gitea docker registry comes to fruition, then we could remap docker pulls without breaking URLs for users). With no. 2, we have infra already in place that we could do this with, and I personally have contributed code to docker's registry (now a CNCF project called distribution). I should note, I am very thankful for docker hub providing bandwidth and storage for us for the past years, and while we now pay them, our cost to them is likely much higher than they recoup from us.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#7557