Split a Docker image reference into registry, namespace, repository, tag and digest, using the rule Docker actually applies rather than counting slashes.
Waiting for an image reference
One per line. Registries, namespaces, tags and digests are all read.
The breakdown appears here
Every reference with the registry, namespace and tag that were filled in for you.
The first path segment is a registry only when it contains a dot or a colon, or is exactly localhost. That one rule is why myteam/app is a Docker Hub repository and myteam.io/app is a private host — and why tooling that splits on the first slash sends pulls to the wrong place.
Docker Image Reference Parser runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
The rule for where a registry ends is genuinely surprising, and it is why reference parsing goes wrong. The first path segment is a registry only if it contains a dot or a colon, or is exactly `localhost`. So `myregistry.io/app` has a registry and `myteam/app` does not — `myteam` is a Docker Hub namespace. A parser that splits on the first slash gets one of those two wrong.
That rule also explains the error people hit when running a local registry: `myregistry:5000/app` works because of the colon, and a registry called plain `registry` without a port does not, because there is nothing to distinguish it from a Hub namespace.
Tag versus digest is the other half. A tag is mutable — the same tag can point at a different image tomorrow, which is what makes `latest` unreproducible and what makes a pinned minor version a compromise rather than a guarantee. A digest is the content hash: it names exactly one image for ever. Pinning by digest is the only form of pinning that cannot move under you.
The canonical fully-qualified form is shown alongside, with the implicit parts filled in — `nginx` is really `docker.io/library/nginx:latest`. Seeing that written out is the quickest way to understand why Docker Hub references look different from everyone else's.
It is a registry only if it contains a dot or a colon, or is exactly `localhost`. Otherwise it is a Docker Hub namespace. That is the whole rule, and it is why `myteam/app` goes to Hub while `myteam.io/app` does not.
`docker.io/library/nginx:latest`. Docker Hub is the implicit registry, `library` is the namespace for official images, and `latest` is the implicit tag. Everything about short references follows from those three defaults.
A digest if you want certainty — it is a content hash and names exactly one image for ever. A tag is mutable and can point somewhere else tomorrow. The trade-off is that updating a digest is a deliberate edit, which is also the point.
Probably because its hostname has no dot and no port, so Docker reads it as a Hub namespace. Adding the port — `registry:5000/app` — gives it the colon it needs.
No. The reference is parsed as a string in your browser. Nothing is fetched, so this cannot tell you whether the image exists.