Freedom251 › Container Registries
Django-OCI
What Django-OCI is
Django-OCI is an open-source Django module for Python developers building registries that follow the OpenContainers Distribution Specification. It provides distribution-spec API endpoints for pushing, pulling, and interacting with container images. Developers can install it with `pip install django-oci` or from a GitHub checkout; installation includes Django Rest Framework. The registry can run locally in a virtual environment or as part of a container-orchestrated registry. Filesystem storage is the default and current option, intended for smaller registries that do not use an external resource such as cloud storage. Authentication follows a Docker-style OAuth 2.0 flow with username and account-token credentials, plus JWT access tokens. Configuration covers the URL prefix, authentication, spec version, allowed content types, storage backend, session and token expiry, authenticated views, request rate limits, and whether manifest tag deletion is allowed. The project does not provide a frontend for viewing containers, and it has no official client; its documentation describes Python Requests and the Reggie client for interacting with a registry. Private repositories and repository ownership or contributors are not yet implemented. The project is in early development, with most stated goals still under development. Users are asked to read and agree to its license before use.
Who it suits
Django-OCI suits Python developers who want to build and deploy a container image registry through Django and distribution-spec API endpoints. It can fit local or container-orchestrated deployments, especially smaller registries using filesystem storage.
What it does well
- Provides endpoints to push, pull, and interact with container images.
- Can run locally or in a container-orchestrated registry.
- Uses OAuth 2.0 credentials and JWT access tokens.
- Offers settings for storage, expiry, and request limits.
- Includes Python tests and documents conformance testing.
What to know first
- There is no frontend for viewing containers.
- Private repositories and ownership or contributors are not implemented.
- Filesystem is the only current storage option.
- Most stated goals remain under development.
Limits
No hosted plan or usage limits are stated for the free, open-source software. The current storage option is filesystem storage; the module has no container-viewing frontend, and private repositories and repository ownership or contributors are not implemented.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Open-source software | No hosted plan or usage limits stated | Free |
As vsoch.github.io lists them, read 11 Oct 2026. The maker's own page has the final word.
Getting started
- Open the Django-OCI website.
- Install the package with `pip install django-oci` or use a GitHub checkout.
- Account for Django Rest Framework, which is installed as a dependency.
- Configure the registry settings, including storage and authentication.
- Deploy locally in a virtual environment or as part of a container-orchestrated registry.
- Use API endpoints with Python Requests or the Reggie client.
Verdict
Choose Django-OCI if you are a Python developer building a registry around its distribution-spec API and are comfortable configuring and deploying the Django module yourself. Look elsewhere if you need a container-viewing frontend, private repositories, ownership controls, or a project whose stated goals are already implemented.
Questions
What does Django-OCI cost?
The Open-source software plan is free. No hosted plan or usage limits are stated.
How can I install it?
Install it as a Python package with `pip install django-oci` or use a GitHub checkout. Installation includes Django Rest Framework.
Does Django-OCI include a frontend or official client?
It does not provide a frontend for viewing containers and has no official client. The documentation describes Python Requests and the Reggie client for registry interactions.
What storage does it support?
Filesystem is the current and default storage option, intended for smaller registries that do not use an external resource such as cloud storage.
How does authentication work?
Authentication uses a Docker-style OAuth 2.0 flow with username and account-token credentials and JWT access tokens. Authentication can be disabled, though the documentation strongly discourages doing so without a specific, strong use case.
Is Django-OCI open source?
The project is described as open source, and its license governs use. Users are asked to read and agree to the project license before using the software.
Facts from Django-OCI's own pages
- API
- It provides distribution-spec API endpoints for pushing, pulling, and interacting with a registry. · vsoch.github.io, 11 Oct 2026
- Authentication
- Authentication uses a Docker-style OAuth 2.0 flow with username and token credentials and expiring JWT bearer tokens. · vsoch.github.io, 11 Oct 2026
- Authentication caution
- The documentation strongly discourages disabling authentication unless there is a specific, strong use case. · vsoch.github.io, 5 Oct 2026
- Client integrations
- There is no official client; the documentation describes Python Requests and the Reggie client as ways to interact with a registry. · vsoch.github.io, 11 Oct 2026
- Compliance
- The policy page encourages developers who create registries to ensure that their registries are GDPR compliant. · vsoch.github.io, 11 Oct 2026
- Configurable controls
- Settings include token and upload-session expiration, authenticated views, request rate limits, and an option to disable manifest tag deletion. · vsoch.github.io, 11 Oct 2026
- Configuration
- Settings include URL prefix, authentication, spec version, allowed content types, storage backend, session and token expiry, and view rate limits. · vsoch.github.io, 5 Oct 2026
- Dependency
- Installation includes Django Rest Framework as a dependency. · vsoch.github.io, 5 Oct 2026
- Deployment
- It can be deployed locally in a virtual environment or as part of a container orchestrated registry. · vsoch.github.io, 5 Oct 2026
- Development status
- The introduction says the project is still in early development and that most stated goals remain under development. · vsoch.github.io, 11 Oct 2026
- Frontend limit
- The module does not provide a frontend interface for viewing containers. · vsoch.github.io, 11 Oct 2026
- Installation
- The package can be installed with pip or from a GitHub clone, and its documented dependency is Django REST Framework. · vsoch.github.io, 11 Oct 2026
- License
- Use is governed by the project license, which users are asked to read and agree to before using the software. · vsoch.github.io, 5 Oct 2026
- No frontend
- The project does not yet provide a frontend interface for viewing containers. · vsoch.github.io, 5 Oct 2026
- Not implemented
- Private repositories and repository ownership or contributors are described as not yet implemented. · vsoch.github.io, 5 Oct 2026
- Privacy guidance
- The policy page encourages registry developers to ensure their registries are GDPR compliant. · vsoch.github.io, 5 Oct 2026
- Purpose
- Django-OCI is an open-source registry module for Python developers using Django to build OCI-compliant registries. · vsoch.github.io, 11 Oct 2026
- Repository privacy
- Private repositories and contributor ownership are described as planned model features that are not yet implemented. · vsoch.github.io, 11 Oct 2026
- Security setting
- Authentication can be disabled, but the documentation strongly discourages doing so except for a specific strong use case. · vsoch.github.io, 11 Oct 2026
- Storage
- Filesystem is the currently supported default storage backend, intended for smaller registries that cannot use an external resource such as cloud storage. · vsoch.github.io, 11 Oct 2026
- Support
- The project asks users who need help to open an issue. · vsoch.github.io, 11 Oct 2026
- Testing
- The project provides Python tests and documents conformance testing through the OpenContainers distribution-spec repository. · vsoch.github.io, 5 Oct 2026
- What it does
- The Django module lets Python developers build OCI compliant registries with endpoints to push, pull, and interact with container images. · vsoch.github.io, 5 Oct 2026
Where Django-OCI stands on Freedom251
- Container Registries#8 of 60