Docker Hub is Docker's hosted public and private container registry, sold through Docker subscriptions with pull rate limits on free use; these pages cover replacing or fronting it with a self-hosted Harbor registry.
A buyer comparison of Docker's hosted registry against a self-hosted Harbor registry: pull limits and per-seat plans versus your own capacity, private repositories, SSO by plan versus Harbor's OIDC and LDAP, Docker Scout versus Trivy scanning, replication and proxy cache, and the operations work Harbor adds.
How to move images off Docker Hub into Harbor: registering Docker Hub as a replication endpoint, pull-based replication rules with name and tag filters, proxy cache projects for public images, repointing CI and Kubernetes pull secrets, and running both registries during cutover.
Cost of ownership by component: Docker's per-user subscription prices and the features gated to Team and Business against Harbor's servers, storage, PostgreSQL and Redis, upgrades, scanning and the engineer time to run it, plus when keeping a paid Docker plan alongside Harbor still makes sense.
Getting repositories and tags out of Docker Hub: listing them through the Docker Hub API with access tokens, pulling every tag and architecture over the registry API with Skopeo or Harbor pull replication, and what counts against pull limits during a bulk export.
Why an isolated network cannot pull from Docker Hub or a Docker Hub mirror, and how a Harbor registry installed from the offline installer, fed by Skopeo or replication through a transfer host, serves images to clusters with no Internet route.
For CI fleets and Kubernetes clusters hitting Docker Hub pull limits: how Docker counts pulls per IP and account, running a Harbor proxy cache project or the official Registry image as a mirror, securing it, and when a paid Docker plan is cheaper.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.