How uber/kraken works
Kraken is a P2P-powered Docker registry: clients push images through a proxy and pull them from agents, which fetch blobs from peers while the tracker coordinates peer discovery. Dedicated origins seed content and bridge local files to pluggable blob backends; build-index resolves tags and supports asynchronous cross-cluster replication. The README establishes the overall component roles; sampled handlers and the source index show selected calls. Some internal wiring and unsampled subsystems are therefore represented only where documented.
Main entry points: manager.go Backend manager · proxyserver/server.go Registry proxy · tagserver/server.go Build-index server · agentserver/server.go Host agent
Components 24
Registry access
- Registry proxy
proxy/proxyserver/server.go - Registry override
proxy/registryoverride/server.go - Host agent
agent/agentserver/server.go - Registry driver
lib/dockerregistry/storage_driver.go
Peer distribution
- Peer tracker
tracker/trackerserver/server.go - Peer announcements
tracker/announceclient/client.go - Peer scheduler
lib/torrent/scheduler/scheduler.go - Piece requests
lib/torrent/scheduler/dispatch/piecerequest/manager.go - Torrent storage
lib/torrent/storage/storage.go
Origin storage
- Origin server
origin/blobserver/server.go - Blob client
origin/blobclient/client.go - Origin cluster
origin/blobclient/cluster_client.go
Tags and replication
- Build-index server
build-index/tagserver/server.go - Tag client
build-index/tagclient/client.go - Tag store
build-index/tagstore/store.go - Replication retries
lib/persistedretry/manager.go
Storage backends
- Backend manager
lib/backend/manager.go - GCS backend
lib/backend/gcsbackend/client.go - HDFS backend
lib/backend/hdfsbackend/client.go - S3 backend
lib/backend/s3backend/client.go - Shadow backend
lib/backend/shadowbackend/client.go - SQL backend
lib/backend/sqlbackend/client.go
Other components
- Docker client
- Remote registry
Connections 28
- Docker client → Registry proxy: pushes images
- Docker client → Host agent: pulls images
- Registry proxy → Origin server: uploads blobs
- Registry proxy → Build-index server: uploads tags
- Registry proxy → Blob client: preheats blobs
proxy/proxyserver/server.go - Registry proxy → Tag client: resolves tags
proxy/proxyserver/server.go - Registry override → Tag client: lists tags
proxy/registryoverride/server.go - Host agent → Tag client: looks up tags
agent/agentserver/server.go - Host agent → Peer scheduler: downloads via P2P
agent/agentserver/server.go - Host agent → Peer announcements: announces content
- Peer scheduler → Peer tracker: requests peers
- Peer scheduler → Piece requests: dispatches pieces
- Peer scheduler → Torrent storage: stores pieces
- Peer tracker → Origin cluster: checks origin readiness
tracker/trackerserver/server.go - Peer tracker → Remote registry: returns ordered peers
- Origin server → Origin cluster: distributes blob load
- Origin server → Backend manager: reads and writes blobs
origin/blobserver/server.go - Origin cluster → Backend manager: uses configured stores
- Backend manager → GCS backend: creates client
lib/backend/manager.go - Backend manager → HDFS backend: creates client
lib/backend/manager.go - Backend manager → S3 backend: creates client
lib/backend/manager.go - Backend manager → Shadow backend: creates client
lib/backend/manager.go - Backend manager → SQL backend: creates client
lib/backend/manager.go - Build-index server → Tag store: stores tag mappings
build-index/tagserver/server.go - Tag client → Build-index server: calls tag API
build-index/tagclient/client.go - Build-index server → Remote registry: replicates tags
- Build-index server → Replication retries: queues replication retries
- Remote registry → Remote registry: receives replicated tags