Skip to main content
There are many pre-built container images available today. Organizations publish their products to public and private registries so teams can pull, run, and scale applications quickly. The most popular public registry is Docker Hub, and other common options include GitHub Container Registry, Google Artifact Registry, AWS ECR, and Azure Container Registry. You can find images for operating systems, databases, developer tools, and full applications on these registries. After installing Docker (or another container runtime) on your host, bringing up an application is often as simple as running a single docker run command with the image name.
A presentation slide titled "Images And Registries" showing a Public Docker Registry section (dockerhub) with example images like Ansible, MongoDB, Redis and Node.js, plus a list of other registries (GitHub, Google, Amazon, Azure). A presenter wearing a KodeKloud t-shirt stands on the right.
Common use patterns
  • Run a single container for development or testing.
  • Launch multiple container instances for scaling or redundancy, then place a load balancer or reverse proxy in front of them.
  • Replace a failed instance by removing the container and starting a new one from the same image.
Example — simple commands starting containers from images (one command per instance):
Note: if Docker cannot find the specified image locally, it will pull the image from the configured registry (for example, Docker Hub). Key concepts: image vs. container Image naming and tags
  • Image names often include a repository and a tag to indicate the version:
    • Example: nginx:1.27
  • If no tag is provided, Docker defaults to the latest tag — avoid relying on latest in production to prevent unexpected upgrades.
Best practices (short list)
  • Use explicit tags for reproducible deployments (for example myapp:2026.10.01).
  • Scan images for vulnerabilities before deploying.
  • Use a private or managed registry for production workloads to control access and retention.
  • Automate builds and push images from CI/CD pipelines to ensure traceability.
Avoid using the latest tag in production. Always pin to an explicit version and test images before promoting them to production environments.
Container registries at a glance Practical tip: starting multiple instances correctly
  • For production or when running many instances locally, you usually want to:
    • Run containers in detached mode (-d).
    • Assign names (--name) or labels for easier management.
    • Expose ports and mount volumes as needed.
Example (better practice):
Links and references
Public registries like Docker Hub host many official and community images. For production, consider using a private or managed registry (AWS ECR, Azure Container Registry, Google Artifact Registry) to control access and manage image lifecycle.

Watch Video