[HN Gopher] Show HN: Container registry on a budget using AWS S3
___________________________________________________________________
Show HN: Container registry on a budget using AWS S3
Author : mborch
Score : 9 points
Date : 2022-02-28 21:37 UTC (1 hours ago)
(HTM) web link (maltheborch.com)
(TXT) w3m dump (maltheborch.com)
| laurencerowe wrote:
| If using AWS why not just use ECR? https://aws.amazon.com/ecr/
| biohax2015 wrote:
| Which uses S3 on the backend anyway..
| mborch wrote:
| 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.
| charcircuit wrote:
| >using S3
|
| He doesn't use AWS S3, but instead digital ocean spaces.
| nhoughto wrote:
| 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?
| xrd wrote:
| 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.
___________________________________________________________________
(page generated 2022-02-28 23:01 UTC)