Hey guys, we’re building a new container registry, which would be fully OCI Distribution Specification compliant. This means that OpenRegistry would be completely compatible with any relatively new version of container engines like Docker, Containerd, Podman, etc.
For the longest time Docker has run Docker Hub and it’s been the most popular platform by far. Majority of the people rely on Docker’s Container Registry. Here’s a few reasons why THIS project comes to life:
- Docker Hub is run by a corporate, who’s biggest (but not only) goal is to make profit
- When Docker Hub goes down, it causes a lot of service degradation for it’s peers, we can show the tech industry how resilient and robust Akash Network is for Fault Tolerant Systems.
- Docker’s new Rate Limiting makes if even hard to use Docker. (I’ve worked with Fortune500 Clients in my previous org and we were literally forced to use AWS’ Container registry)
- Run by the Open Cloud, powered by Open Technologies. We’re planning to add IPFS support soon after the initial launch.
Initially OpenRegistry would be built on top of Skynet for the storage backend but the OCI Distribution Spec defines the backend to be pluggable simply by satisfying the
storage.StorageDriver backend. Once the MVP is ready, we’d go on to add multiple storage backends.
Q. How difficult it would be to use this registry?
Answer: OpenRegistry would be fully OCI Distribution Spec compliant, that means your existing workflow would remain exactly how it is.
PS: No offense to Docker Hub. Docker hub is what most of us use and so do I. I absolutely loved what Docker stood for a while ago but now their vision has changed.