Hmm.
> GitHub's Container Registry offers free storage for public images.
But for how long?
> GitHub's Container Registry offers free storage for public images.
But for how long?
the subtitle of the web era
And their entire marketing strategy is built around free hosting for public data, so it'd take a major shift for this to disappear. Not to say it's impossible, but it seems like the best bet of the options available.
Is it practical to set up a redirect in front of a Docker registry? To make your images available at example.com/docker-images/abc, but just serve an HTTP redirect that sends clients to ghcr.io/example-corp/abc? That way you could pick a new host now, and avoid images breaking in future if they disappear or if you decide to change.
Shouldn't be any security risk there AFAICT. Just hard to tell if it's functionally supported by typical registry clients or if there are other issues that'd appear.
If they choose. It's in fashion right now to fire people and squeeze free tiers.
I don't know if container signature tools support multiple registry locations though.
1. Embrace
2. Extend <- you are here
3. Extinguish
Can we stop this madness already?
applies very much to Github, and for all of their services, not just containers. The elephant in the room, hardly needs to be mentioned I would think (Microsoft). We are only a few years into that regime.
Free to existing Windows users, perhaps, but free to the world doesn’t seem like something Microsoft was historically in a position to offer, much less later kill.