- Home
- Container Registries
- Distribution Registry
On the recordRead 11 Oct 202622 facts
Distribution Registry
On the record
- Advanced access control
- Delegated authentication is supported, but requires implementing or using a third-party authentication system.distribution.github.io · read 10 Oct 2026
- Advanced authentication
- The Registry supports delegated authentication through a trusted token server for deployments needing more control over access control and authorization integration.distribution.github.io · read 11 Oct 2026
- 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.distribution.github.io · read 11 Oct 2026
- API
- The documentation provides an HTTP API V2 specification for interacting with the registry.distribution.github.io · read 10 Oct 2026
- 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.distribution.github.io · read 10 Oct 2026
- Compatibility
- The Distribution Registry implements OCI Distribution Spec version 1.0.1.distribution.github.io · read 11 Oct 2026
- Driver limits
- New storage drivers are not currently being accepted, and the OSS and Swift drivers are no longer supported.distribution.github.io · read 10 Oct 2026
- Image workflows
- Users interact with a registry by pushing and pulling images, which are available in tagged versions.distribution.github.io · read 11 Oct 2026
- 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.distribution.github.io · read 11 Oct 2026
- Intended use
- The project is aimed at teams that want control over image storage, their distribution pipeline, or integration with in-house development workflows.distribution.github.io · read 10 Oct 2026
- License
- The Registry is open source under the permissive Apache license.distribution.github.io · read 11 Oct 2026
- Monitoring
- The Registry includes logging and reporting, and notification endpoint status and metrics are exposed through its debug/vars interface.distribution.github.io · read 10 Oct 2026
- Notification limitation
- Notification queues are in memory, so messages can be lost if a registry instance is lost before delivery.distribution.github.io · read 10 Oct 2026
- Notifications
- The Registry includes a notification system that calls webhooks in response to activity, along with logging and reporting.distribution.github.io · read 11 Oct 2026
- OCI compatibility
- The registry implements OCI Distribution Specification version 1.0.1.distribution.github.io · read 10 Oct 2026
- Operational requirements
- Production operation requires skills in availability, scalability, logging, monitoring, and security; familiarity with Docker and networking is also required.distribution.github.io · read 11 Oct 2026
- Purpose
- Distribution Registry is a stateless, highly scalable server-side application for storing and distributing container images and other content.distribution.github.io · read 11 Oct 2026
- Security
- The Registry natively supports TLS and basic authentication; externally accessible registries must first be secured using TLS.distribution.github.io · read 11 Oct 2026
Alternatives to Distribution Registry
Inedo ProGetWebWindows+3JFrog Container RegistryWebWindows+3Volcengine Container RegistryAndroidiPhone & iPad+5Samsung Cloud Platform Container RegistryAndroidiPhone & iPad+3Chainguard RegistryWebLinux+18gears Container RegistryWebLinux+2Alibaba Cloud Container RegistryWebWindows+2KakaoCloud Container RegistryWebMac+2
