Any recommended alternatives to Harbor?

Hey Webert! The tooling landscape lists 6 alternatives and the CNCF landscape has even more in that category. There are even more out there, but which one you should choose is heavily dependent on your requirements. So until you spill your beans on where you want to run it, if commercial is an option and if you have requirements beyond “will store my images”, the basic answer will be “yes” 🙂

Thanks @Clemens Jütte yeah I should have been more specific, haha. I started from that box and I dismissed a few options from there: • Docker, JFrog (cloud) - loosely integrated with our runtime environment • Jfrog (self hosted) - I have had only bad experiences with it • ECR - not much flexibility in terms of domain configuration and requires short-lived token authentication, not suitable for some of my systems • Azure, GCP registries - I haven't used them but I believe they must work similar to AWS ECR. So the only option that seems to be left for me is Harbor.

Harbor and Quay are both alternatives that are possible but complex beasts - Harbor comes out first in my personal book. If you don’t need the complexity, then getting a managed service is the way better option. Google registry has been trusty and painless for me. You can use service user keys to access which are long-lived.

I was curious and did a search for OCI-compliant registries. I came across Zot and its ecosystem. It’s a single binary. The example shows it being used with auth disabled. https://zotregistry.dev/v2.1.0/user-guides/user-guide-datapath/

Interesting, accepted as Sandbox in CNCF, thanks for sharing it @Pete Warnock

This must be a slightly stupid question, but what's wrong with Azure, GCP registries and AWS ECR? Lack of features? cost? Compliancy? Seems i've never seen the need to use anything else

not a stupid question at all, a good point frankly. many companies i interview depend on the big 3 registries for container hosting. harbor is cloud agnostic which is important to a certain signature of client portability stories, but many would say that since they’ll have a foot in the one of the big 3 clouds anyway, they just lean on ecr/gcr for the easy solution with high 9s. github and gitlab saas also have container hosting available through their git repository ecosystems. for a self managed cheap and easy solution, many get away with a simple docker registry image running in kubernetes pod. a lot depends on what features you need out of your image registry.