image reference
The full name used to find an image: registry, namespace, repository, then a tag or digest.
In more detail
Read registry.example.com/team/web:1.0 from left to right: registry host, namespace, repository, tag. Leave out the registry and Docker assumes Docker Hub; leave out the namespace and it assumes library, the home of Docker Official Images; leave out the tag and it assumes latest. None of those defaults make an image trustworthy by themselves.
Related terms
- registry — A server that stores images and lets clients push and pull them by name, tag or digest.
- image namespace — The part of an image name that says which person or organisation owns it, such as team in registry.example.com/team/app.
- image repository — A named collection of related images in a registry, told apart by their tags, such as python with tags 3.12 and 3.13.
- tag — A human-readable label such as 3.20 or latest attached to an image in a repository, which can be moved to point at a different image.
- digest — A SHA-256 hash of an image's manifest that identifies its exact content and can never be moved to other bytes.
- Docker Official Image — A curated image on Docker Hub, such as alpine or python, maintained with documented, reviewed build files.
Taught in
- Pull And Inspect A Third Party Image — Docker Architecture & Production Containers
- CMD, ENTRYPOINT, USER And Process Signals — Docker Architecture & Production Containers
- Tags, Digests And Reproducible Image References — Docker Architecture & Production Containers
- Authenticate, Tag, Push And Pull From A Registry — Docker Architecture & Production Containers
- Scan, Patch And Inspect The Software Supply Chain — Docker Architecture & Production Containers
- Define The Service And Database With Compose — Docker Architecture & Production Containers
- Troubleshooting: ImagePullBackOff And Failed Rollouts — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: A Timed Service Recovery Drill — Kubernetes: Production-Grade Container Orchestration