Distribution Registry
distribution.github.io
- Free plan
- Windows
- macOS
- Linux
- API
- Self-hosted
7.6 Club score Visit distribution.github.io
What the maker publishes
- Advanced access control
- Delegated authentication is supported, but requires implementing or using a third-party authentication system. source
- Advanced authentication
- The Registry supports delegated authentication through a trusted token server for deployments needing more control over access control and authorization integration. source
- Air-gapped use
- A Registry can run without internet connectivity, but images that are not local may need to be fetched on a connected host and migrated into the isolated network. source
- API
- The documentation provides an HTTP API V2 specification for interacting with the registry. source
- Authentication and transport security
- The Registry supports TLS and basic authentication; its deployment guide says externally accessible registries must be secured with TLS and should use access controls. source
- Compatibility
- The Distribution Registry implements OCI Distribution Spec version 1.0.1. source
- Driver limits
- New storage drivers are not currently being accepted, and the OSS and Swift drivers are no longer supported. source
- Image workflows
- Users interact with a registry by pushing and pulling images, which are available in tagged versions. source
- Integrations
- A typical CI/CD workflow can push a new image to the Registry after a successful build, then use a Registry notification to trigger deployment or notify other systems. source
- Intended use
- The project is aimed at teams that want control over image storage, their distribution pipeline, or integration with in-house development workflows. source
- License
- The Registry is open source under the Apache license. source
- License
- The Registry is open source under the permissive Apache license. source
- Monitoring
- The Registry includes logging and reporting, and notification endpoint status and metrics are exposed through its debug/vars interface. source
- Notification limitation
- Notification queues are in memory, so messages can be lost if a registry instance is lost before delivery. source
- Notifications
- The Registry includes a notification system that calls webhooks in response to activity, along with logging and reporting. source
- OCI compatibility
- The registry implements OCI Distribution Specification version 1.0.1. source
- Operational requirements
- The project says production operation requires skills in availability, scalability, logging, monitoring, and security. source
- Operational requirements
- Production operation requires skills in availability, scalability, logging, monitoring, and security; familiarity with Docker and networking is also required. source
- Purpose
- Distribution Registry stores and distributes named container images and other content. source
- Purpose
- Distribution Registry is a stateless, highly scalable server-side application for storing and distributing container images and other content. source
- Security
- The Registry natively supports TLS and basic authentication; externally accessible registries must first be secured using TLS. source
- Storage
- Bundled storage drivers support the local filesystem, Amazon S3, Microsoft Azure Blob Storage, and Google Cloud Storage. source
- Storage
- The default storage driver is the local POSIX filesystem; supported cloud storage drivers include S3, Microsoft Azure, and Google Cloud Storage. source
- Storage driver limitation
- Adding support for new storage drivers has been put on hold; the documentation suggests considering whether a desired driver is S3 compatible. source
Checked against the maker's pages on 11 Oct 2026.