Running our Docker registry on-prem with Harbor
dev.37signals.com
Running our Docker registry on-prem with Harbor
1–10 of 78 posts
Re: Running our Docker registry on-prem with Harbor
#2Re: Running our Docker registry on-prem with Harbor
#3Re: Running our Docker registry on-prem with Harbor
#4Re: Running our Docker registry on-prem with Harbor
#5Re: Running our Docker registry on-prem with Harbor
#6Contrary to the author of this post, we just run one (the "source of truth") and use caching proxies in other regions. Works fine for us.
Re: Running our Docker registry on-prem with Harbor
#7Why does the Harbor VM need 32 cores and 64GB of RAM? Especially if it's only serving 32,000 pulls over 2 months.
Hell Git doesn't even need the Git protocol if you do `update-server-info`
Re: Running our Docker registry on-prem with Harbor
#8I also run Harbor. I use the official Helm chart; it's a little jank, doesn't support a couple of things we want. It only works with one of ArgoCD/ExternalSecretsOperator, and it doesn't support Redis TLS. Contrary to the author of this post, we just run one (the "source of truth") and use caching proxies in other regions. Works fine for us.
Re: Running our Docker registry on-prem with Harbor
#9Why does the Harbor VM need 32 cores and 64GB of RAM? Especially if it's only serving 32,000 pulls over 2 months.
Re: Running our Docker registry on-prem with Harbor
#10harbor is great ... simple to install ... it's the only container registry I ever use