Distribution Registry vs Django-OCI
Distribution Registry
distribution.github.ioDjango-OCI
vsoch.github.ioSide by side
| Figure | Distribution Registry | Django-OCI |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · Container Registries | 7.8 (#16) | 8.6 (#4) |
| API | The documentation provides an HTTP API V2 specification for interacting with the registry. | It provides distribution-spec API endpoints for pushing, pulling, and interacting with a registry. |
| License | The Registry is open source under the permissive Apache license. | Use is governed by the project license, which users are asked to read and agree to before using the software. |
| Purpose | Distribution Registry is a stateless, highly scalable server-side application for storing and distributing container images and other content. | Django-OCI is an open-source registry module for Python developers using Django to build OCI-compliant registries. |
| Storage | The default storage driver is the local POSIX filesystem; supported cloud storage drivers include S3, Microsoft Azure, and Google Cloud Storage. | Filesystem is the currently supported default storage backend, intended for smaller registries that cannot use an external resource such as cloud storage. |
| Support | The project directs users to its #distribution channel in CNCF Slack for help and its GitHub issue tracker to report bugs. | The project asks users who need help to open an issue. |
Plans
In their own words
Distribution Registry
Distribution Registry has no write-up on Specifiction yet; its figures are above.
Django-OCI
Django-OCI is free, open-source software for Python developers building registries that follow the OpenContainers Distribution Specification. The Django module exposes API endpoints for pushing, pulling, and interacting with container images, and can run in a virtual environment or within a container-orchestrated registry. Installation is available through pip or a GitHub checkout and includes Django Rest Framework. Filesystem storage is the default option, intended for smaller registries without external cloud storage. Authentication uses a Docker-style OAuth 2.0 flow with username and account-token credentials plus JWT access tokens. Configuration covers URL prefixes, specification version, content types, storage, authentication, token and session expiry, request limits, and manifest-tag deletion. There is no frontend for viewing containers. Private repositories and repository ownership or contributors are not implemented. The project is described as early development, with most goals still under development. Python tests and distribution-spec conformance testing are documented. Developers are asked to consider GDPR compliance, open an issue for help, and review the project license before use.