Django-OCI vs openSUSE Registry
Django-OCI
vsoch.github.ioopenSUSE Registry
registry.opensuse.orgSide by side
| Figure | Django-OCI | openSUSE Registry |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Linux | Yes | Yes |
| API | Yes | — |
| Self-hosted | Yes | — |
| Plans published | 1 | 0 |
| Spec score · Container Registries | 8.6 (#4) | 6.7 (#47) |
| Purpose | Django-OCI is an open-source registry module for Python developers using Django to build OCI-compliant registries. | The Registry page describes itself as a place to find container images built by the Open Build Service. |
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.
openSUSE Registry
openSUSE Registry has no write-up on Specifiction yet; its figures are above.