Django-OCI vs olareg
Django-OCI
vsoch.github.ioolareg
olareg.orgSide by side
| Figure | Django-OCI | olareg |
|---|---|---|
| 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 | 1 | 0 |
| Spec score · Container Registries | 8.6 (#4) | 7.4 (#32) |
| Authentication | Authentication uses a Docker-style OAuth 2.0 flow with username and token credentials and expiring JWT bearer tokens. | The documentation describes basic authentication and opaque token authentication; opaque tokens expire after five minutes. |
| Deployment | It can be deployed locally in a virtual environment or as part of a container orchestrated registry. | olareg can be deployed as a container image, a standalone binary, or used as a Go package. |
| Purpose | Django-OCI is an open-source registry module for Python developers using Django to build OCI-compliant registries. | olareg is a minimal OCI conformant container registry designed around the OCI Layout structure for storing images in a directory. |
| Storage | Filesystem is the currently supported default storage backend, intended for smaller registries that cannot use an external resource such as cloud storage. | It supports directory storage and ephemeral in-memory storage. |
| Testing | The project provides Python tests and documents conformance testing through the OpenContainers distribution-spec repository. | The project is designed to be embedded in Go unit tests as a simple registry for testing tools that work with container registries. |
Plans
In their own words
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.