

I’ve only done my “is it even possible” research so far, but these look promising:
https://medium.com/@amandubey_6607/docker-registry-caching-a2dfefecfff5
I’ve only done my “is it even possible” research so far, but these look promising:
https://medium.com/@amandubey_6607/docker-registry-caching-a2dfefecfff5
Huh. I was just considering establishing a caching registry for other reasons. Ferb, I know what we’re going to do today!
Others are posting the well written explanations, so I’ll make the short comparisons.
GitHub is like Reddit is to Lemmy. It’s the main player in source code hosting, proprietary and centralized to the profits and whims of Microsoft. But for that cost, you can easily bet a project you are looking for has a presence there, and it’s easier for a dev to pop from project to project with one account and identity.
The others are like Lemmy, meant for hosting your own GitHub-like website with all the bells and whistles on top of the standard Git codeshare. There’s a lot of feature parity, though some softwares have more than others. But it comes at the cost of obscurity, Codeberg is a big player but any instance you find is isolated, and any devs you entice to help you need to register additional accounts personal to that instance. And the hosting costs are on you, it can all vanish with an unpaid domain/server bill unlike the central giant of GitHub.
Gitea and therefore Forgejo also have container registry functionality, I use that for private builds.