How-to guides

Recipes for specific container-registry tasks.

• Cache images for CI

  Put peryx between your runners and Docker Hub: pull base images through one cache, and stop hitting the anonymous pull-rate limit.

• Compose a virtual registry

  Stack a hosted store over a cached Docker Hub proxy so your own images shadow same-named upstream ones, the dependency-confusion defense for containers.

• Proxy a private registry

  Cache a private or authenticated upstream registry (GHCR, ECR, Harbor, or an Artifactory /v2/) through peryx, supplying upstream credentials.

• Serve images air-gapped

  Run peryx as a container registry on a network with no path to Docker Hub: pre-seed a cache, then run offline or carry the data directory across the gap.

• Run a container registry

  Proxy Docker Hub, host your own images, and shadow upstream with a virtual index, then pull and push with docker, podman, or crane.