6 ms·
Hmm. > GitHub's Container Registry offers free storage for public images. But for how long?
by nottorp 4y ago
Hmm.
> GitHub's Container Registry offers free storage for public images.
But for how long?
- agumonkey 4y ago> But for how long? the subtitle of the web era
- preciousoo 4y agoThe hippies were right
- Kwpolska 4y agoThey have a pretty good track record in code hosting (15 years), why would they ruin it for containers?
- bflesch 4y agoGithub shutting down is not on my risk matrix. Hopefully it happens after I retire.
- tankerkiller 4y agoIt's on ours where I work, which is why we use Gitea to clone the various open source projects we use to our own servers. With binary level deduplication the amount of data stored is actually incredibly small. I think the unduplicated storage is like 50GB, and the deduplicated is like 10GB?
- jnwatson 4y agoThe 6-8 orders of magnitude difference in storage required?
- bmacho 4y agoWe need a culture to not use resources even if it is available and cheap. Use github like it wasn't free.
- trey-jones 4y ago> But for how long? 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.
- Sebb767 4y agoYou can say a lot of bad stuff about Microsoft, but they are not known for randomly and suddenly killing of their services.
- macintux 4y agoSerious question, though: how many services have they offered over the years that were free to anyone? 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.
- trey-jones 4y agoIt's not randomly and suddenly killing off services, but rather suddenly (and not randomly) changing the pricing structure when companies have been committing to the point of lock-in for years on the free tier.
- pimterry 4y agoUnlike Docker Inc, GitHub (via Microsoft) do have very deep pockets & their own entire cloud platform, so they can afford to do this forever if they choose. 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.
- shaunn 4y agoI like where your head is at; I found this [1] and it makes a case that an attack vector may be created. [1] https://stackoverflow.com/a/67351972 https://stackoverflow.com/a/67351972
- pimterry 4y agoThat's different - that's about changing the _client_ configuration. I'm looking to change the server instead, so that the client can use an unambiguous reference to an image, but end up at different registries depending on the server configuration. In a perfect world, Docker Hub would let you do this to migrate community projects away, but even just being able to manually change references now to a registry-agnostic URL would be a big help. 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.
- nottorp 4y ago> so they can afford to do this forever if they choose. If they choose. It's in fashion right now to fire people and squeeze free tiers.
- wvh 4y agoA simple vanity domain solution, like for Go packages, seems like it could work. Just redirect the whole URL directly to the actual registry's URL. I don't know if container signature tools support multiple registry locations though.