What registry features do you lose doing it this way? a normal registry isn't just serving dumb files is it? It is essentially an API that can find images by tags, sha256 etc against a backend. It manages lifecycling of things as they are replaced etc.
I imagine you could live without or substitute some of these features but are there any showstoppers?
While ECR costs a lot less than DigitalOcean's container registry service, they still charge 5x more over AWS S3. I suppose if you need encryption? Seems like they provide some value-add that some users might need.
This project was mostly just a they said it couldn't be done kind of thing.
running a kubernetes cluster is what bloggers call "technology minimalism" these days? joking aside, i've been trying to find some time to mess around with nerdctl's ipfs functionality, seems like it may be a better fit for smaller teams and the self-hosters out there.
Comments
I run multiple registries using dokku. It's very easy and you can host whatever else you want on dokku.
I made mine be public on one host and private with http htpasswd access. This requires changing the nginx file. But it works great.What registry features do you lose doing it this way? a normal registry isn't just serving dumb files is it? It is essentially an API that can find images by tags, sha256 etc against a backend. It manages lifecycling of things as they are replaced etc.
I imagine you could live without or substitute some of these features but are there any showstoppers?
Perhaps container vulnerability scanning? That’s probably a showstopper for most large customers.
You could probably bridge most or all of these with lambdas/workers
If using AWS why not just use ECR? https://aws.amazon.com/ecr/
While ECR costs a lot less than DigitalOcean's container registry service, they still charge 5x more over AWS S3. I suppose if you need encryption? Seems like they provide some value-add that some users might need.
This project was mostly just a they said it couldn't be done kind of thing.
Which uses S3 on the backend anyway..
He doesn't use AWS S3, but instead digital ocean spaces.
running a kubernetes cluster is what bloggers call "technology minimalism" these days? joking aside, i've been trying to find some time to mess around with nerdctl's ipfs functionality, seems like it may be a better fit for smaller teams and the self-hosters out there.
fyi: https://container-registry.com/ is offering free private repos for individuals and small teams.
My poor-man’s container registry: Linux box + SSH + makefile
It sounds like you're just describing a build server and it's filesystem.
i just run mine on my raspberry pi, use ddns and allow specific servers to access it...thats a budget.