project-angos/angos has 83 GitHub stars and 9 forks. GitHot measured 0 stars in 24 hours and +3 in 7 days. Last checked 2026-11-15 20:40 UTC. Last push 2026-11-02.
What you can do
- OCI 1.1 compliant: Docker, Podman, containerd and any OCI tool, with referrers for signatures and SBOMs
- Pull-through cache: mirror Docker Hub, ghcr.io or any upstream; immutable tags skip the upstream check
- Replication: mirror repositories to downstream registries in both directions, with a durable retry queue
- Access policies: CEL expressions decide who may push, pull or delete, per repository, with optional webhook authorization
Measured star growth
- in 24h
- 0
- in 7 days
- +3
- in 15 days
- Update delayed
- in 1 month
- Update delayed
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
About
An OCI-compliant and Docker-compatible container registry.
Developer ToolsREADME.md
OriginalAngos
A container registry that's simple to run and a pleasure to use.
Angos is an OCI registry you configure in one file and run without a database. Its web UI shows what is inside every image, layer by layer, with scan reports and pull history alongside.
The web UI in turn: an image's merged filesystem, the secrets found in its layers, a file compared with the layer below, a vulnerability report, and pull history.
Little to look after
There is no database or lock service to run beside Angos. Everything it knows lives in the storage that holds your images, a directory or an S3 bucket.
- Servers are disposable: start another instance on the same storage and it serves everything the last one did.
- Scale by adding replicas: replicas share the same bucket, with nothing to coordinate them.
- Maintenance while it serves: garbage collection, scrub and prune run beside the live registry.
- Changes without restarts: the configuration and TLS certificates reload when their files change.
Features
- OCI 1.1 compliant: Docker, Podman, containerd and any OCI tool, with referrers for signatures and SBOMs
- Pull-through cache: mirror Docker Hub, ghcr.io or any upstream; immutable tags skip the upstream check
- Replication: mirror repositories to downstream registries in both directions, with a durable retry queue
- Access policies: CEL expressions decide who may push, pull or delete, per repository, with optional webhook authorization
- Passwordless CI: OIDC from GitHub Actions, Kubernetes or any issuer, a token service, and mTLS client certificates
- Retention: keep tags by age, semver pattern, or recent pushes and pulls
- Immutable tags: protect release tags from being overwritten, with exclusions
- Vulnerability scanning: Trivy or Grype on push, the report kept next to the image as an OCI referrer
- Event webhooks: required, optional or asynchronous delivery of push and delete events
- Web UI: browse repositories, manifests, referrers, pull history and image filesystems
- Written in Rust, with no unsafe code
Quick Start
# Create a minimal config
cat > config.toml << 'EOF'
[server]
bind_address = "0.0.0.0"
port = 8000
[blob_store.fs]
root_dir = "./registry-data"
[global.access_policy]
default = "allow"
[repository."test"]
EOF
# Run the registry
./angos -c config.toml server
# Push an image
docker tag alpine:latest localhost:8000/test/alpine:latest
docker push localhost:8000/test/alpine:latest
See the Quickstart Tutorial for a complete walkthrough.
Documentation
The complete documentation index lives in doc/index.md.
Tutorials
- Quickstart - Get a registry running in 5 minutes
- Your First Private Registry - Add authentication and access control
- Mirror Docker Hub - Set up a pull-through cache
How-To Guides
- Deploy with Docker Compose
- Deploy on Kubernetes
- Configure mTLS
- Configure GitHub Actions OIDC
- Push from GitHub Actions
- Configure OIDC
- Set Up Access Control
- Configure Retention Policies
- Protect Tags with Immutability
- Configure Webhook Authorization
- Configure Event Webhooks
- Scan Images with an External Scanner
- Explore Image Filesystems
- Configure Replication
- Run Storage Maintenance
- Enable Durable Cache Jobs
- Enable the Web UI
- Troubleshoot Common Issues
- Upgrade Angos
Reference
- Configuration Reference
- CLI Reference
- CEL Expressions Reference
- API Endpoints Reference
- Web UI Reference
- Event Webhooks Reference
- Metrics Reference
Understanding Angos
- Architecture Overview
- Storage Backends
- Authentication and Authorization
- Pull-Through Caching
- Bi-Directional Replication
- Security Model
Upgrading
Version-specific migration notes are in the Upgrade guide.
Usage
Usage: angos [-c <config...>] <command> [<args>]
An OCI-compliant and docker-compatible registry service
Options:
-c, --config path to a configuration file, repeatable to merge several
with later files winning, defaults to `config.toml`
--help, help display usage information
Commands:
argon Hash a password following the argon2id algorithm
prune Enforce retention policies and reclaim aged upload-lifecycle
leftovers
reconcile Reconcile stored content with the configuration
scrub Walk the store, repair inconsistencies, and quarantine
unrecognized objects
server Run the registry listeners
scanner Run the scanner service that answers scan jobs with SARIF
reports
worker Process durable background jobs
Additional Endpoints
In addition to the standard OCI Distribution endpoints:
/healthz: Liveness health check endpoint/readyz: Readiness health check endpoint/metrics: Prometheus metrics endpoint