docker-registry-ui VS Harbor

If it's only the UX you care about then you can use the docker registry image which supports arm64 and then use a ux like docker-registry-ui and have a nice ui.

I didn't know Fleet. For my own images repos (not Dockerhub hosted) I use Docker Registry UI (on top of registry:2). It's tiny and works perfectly fine.

# required to avoid HTTP 411: see Issue #1486 (https://github.com/moby/moby/issues/1486) chunked_transfer_encoding on; # required for strict SNI checking: see Issue #70 (https://github.com/Joxit/docker-registry-ui/issues/70) proxy_ssl_server_name on; proxy_buffering off; proxy_ignore_headers "X-Accel-Buffering";

I use the default Docker registry container, but with Docker Registry UI.

I’m not familiar with jfrog/artifactory but I self-host a registry on my network. I use joxit/docker-registry-ui for visualization. This is just a frontend on the API provided by the docker registry. AFAIK catalog is the best way to list the images

cat << EOF wget \ https://github.com/goharbor/harbor/releases/download/v2.9.4/\ harbor-offline-installer-v2.9.4.tgz EOF

Now that you know a little more about Cosign, Notary, and DCT, we will take it one step further by using one of these tools: Cosign. For this example, we will use the simple Docker registry:2 reference image to run a simple registry. In a real-world scenario, a managed registry such as Harbor, Amazon ECR, Docker Hub, etc.

Have a look at harbor, you can also use it to follow the same methods for helm charts etc.

Or for something more advanced https://goharbor.io/

Look at https://goharbor.io/

You can host your own image repo if your feeling feisty. Harbor is a graduated project from the CNCF and they are also working on a new implementation called Dragonfly. https://goharbor.io/

Does anybody know whether there could be something like an open/libre container registry?

Maybe the cloud native foundation or the linux foundation could provide something like this to prevent vendor lock-ins?

I was coincidentially trying out harbor again over the last days, and it seems nice as a managed or self-hosted alternative. [1] after some discussions we probably gonna go with that, because we want to prevent another potential lock-in with sonarpoint's nexus.

Does anybody have similar migration plans?

[1] https://goharbor.io

2) Harbor instance registry