Show HN: Container registry on a budget using AWS S3 (opens in new tab)

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?

If using AWS why not just use ECR? https://aws.amazon.com/ecr/

My poor-man’s container registry: Linux box + SSH + makefile

I run multiple registries using dokku. It's very easy and you can host whatever else you want on dokku.

  dokku apps:create registry
  dokku git:from-image registry
  dokku proxy:ports-remove http:5000:5000 
  dokku proxy:ports-add http:80:5000
  dokku nginx:set client-max-body-size 1000m
  dokku ps:restart
  dokku proxy:report

I made mine be public on one host and private with http htpasswd access. This requires changing the nginx file. But it works great.

>using S3

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.

i just run mine on my raspberry pi, use ddns and allow specific servers to access it...thats a budget.