Service type
App service
App service
Distribution Registry service
Self-hosted OCI container registry service built on CNCF Distribution, with persistent or object storage and an optional Valkey or Redis metadata cache.
Use it as a reusable, versioned service inside custom or predefined stacks so teams can keep the runtime and operational model consistent.
Overview
Technical profile and packaging
This page shows how Distribution Registry is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.
Versions
3.1
Source repository
Public Helm chart
Ports and protocols
5000/HTTP
Labels
distribution, registry, oci-registry
Persistent volumes
Registry data
Stacks
Use it inside ready-made stacks or your own
These public stacks already include Distribution Registry as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.
Runtime wiring
Reuse connectivity, storage, and runtime defaults
This service can expose ports, connect to other services, attach persistent storage, and define runtime defaults that become reusable inside stacks rather than being rebuilt case by case.
Endpoints
5000/HTTP
Technical domains
HTTP endpoints from this service can use technical domains with auto-renewed TLS certificates on Wodby.
Volumes
Registry data
Settings
4 settings can be overridden per environment.