# SparkCR

> SparkCR accelerates Docker/OCI image pulls, supports authenticated access with tokens, and can connect private registries for pull or push workflows.

SparkCR helps developers and platform teams pull public and private container images through its registry address. Use the public documentation links below as the canonical source for setup and troubleshooting.

## Core Pages

- [Home](https://sparkcr.cn/): Product overview for SparkCR container image acceleration.
- [Pricing](https://sparkcr.cn/pricing): Plans and usage model for image caching and team traffic.
- [Network Check](https://sparkcr.cn/network): Public IP, peering, quota, and risk-state diagnostics.

## Documentation

- [Quickstart](https://sparkcr.cn/docs/quickstart.md): Pull a public Docker image through SparkCR immediately without signing in or changing runtime configuration.
- [Docker Configuration](https://sparkcr.cn/docs/docker.md): Use explicit Docker Hub alias references for authenticated Docker pulls and understand transparent mirror authentication limits.
- [Registry Reference](https://sparkcr.cn/docs/registry-reference.md): Image reference formats for Docker Hub, GHCR, Quay, GCR, Kubernetes Registry, Elastic, NVIDIA, and private registries.
- [Runtime Configuration](https://sparkcr.cn/docs/runtime-config.md): Configure containerd, Podman, and CRI-O to use SparkCR.
- [Kubernetes](https://sparkcr.cn/docs/kubernetes.md): Configure Kubernetes clusters and image pull secrets for SparkCR.
- [CI/CD](https://sparkcr.cn/docs/ci-cd.md): Use SparkCR in build pipelines and deployment workflows.
- [Private Registries](https://sparkcr.cn/docs/private-registries.md): Connect private registries and configure pull or push access.
- [Cache and Usage](https://sparkcr.cn/docs/cache-and-usage.md): Understand cache behavior, quota usage, pull history, and rate-limit headers.
- [FAQ](https://sparkcr.cn/docs/faq.md): Troubleshoot authentication, 429 limits, image paths, private registry access, and CI failures.

## Usage Notes

- Public image pulls may work anonymously but are subject to anonymous IP quota and risk controls.
- Long-running use, CI workloads, and shared egress networks should authenticate with a SparkCR Access Token.
- Docker users who need signed-in quota or account benefits should pull through the explicit SparkCR Docker Hub alias; Docker Engine `registry-mirrors` pulls may be treated as anonymous.
- Docker Hub official images must include the `library/` namespace when using explicit SparkCR paths.
- Private registry access requires a connected private registry and tokens with `pull:private` or `push`.

## Excluded Content

Do not treat console, admin, audit, billing internals, risk-control internals, or private workspace pages as public documentation. Public AI-facing guidance should come from the pages listed above.