liveBook · Manning

Container registry

A container registry is a service or repository for storing, managing, and distributing container images and related artifacts.

How 8 Manning books explain it

Learn Docker in a Month of Lunches, Second Edition

A container registry is a service that stores and distributes container images.

How it is used
Distributes container images between development machines, build pipelines, and deployment environments.
How deep it goes
Works through image references, login, tagging, pushing, local-registry setup, and cloud use; it does not detail registry server internals.
Examples
Uses Docker Hub image pulls and pushes, a registry container, Azure Container Registry, and GitHub Container Registry staging images.
What you can do after
Operate/configure a registry workflow to tag, push, and pull images through Docker Hub or a local registry.

Read how Learn Docker in a Month of Lunches, Second Edition explains container registry →

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

A container registry is a service that stores, manages, and distributes container images, with access controls such as private repositories.

How it is used
Provides a private cloud location for publishing microservice images that a Kubernetes cluster can obtain for deployment.
How deep it goes
Works through registry creation, authentication, tagging, pushing, pull validation, and cluster access; does not detail registry service internals.
Examples
Uses a video-streaming image, Azure Container Registry, Docker commands, a Terraform registry resource, and an AcrPull role assignment.
What you can do after
Operate/configure a private Azure registry, publish an image with Docker, and make it available to a cloud Kubernetes cluster.

Read how Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform explains container registry →

Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more

A container registry is a service that stores, distributes, and serves container images.

How it is used
Stores and distributes container images for Podman workflows that build, run, share, and deploy containerized applications.
How deep it goes
Traces image layers, manifests, transports, and runtime handoff while deferring advanced registry controls to later treatment.
Examples
Demonstrates quay.io, docker.io, registry.access.redhat.com, short-name selection, podman pull, podman run, and podman push.
What you can do after
Operate/configure registries by pulling, pushing, naming, selecting, inspecting, and controlling image sources with Podman.

Read how Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more explains container registry →

Road to Kubernetes

A container registry is a storage and distribution service for container images.

How it is used
Supports packaging, sharing, and deploying container images across machines and production systems.
How deep it goes
Explains registry purpose, default behavior, account setup, authentication, image tagging, and pushing, but defers self-hosted registry operation.
Examples
Uses Docker Hub, the official NGINX image, docker run nginx, and a tagged Python application image.
What you can do after
Operate Docker Hub by logging in, building a tagged image, pushing it, and pulling images for container execution.

Read how Road to Kubernetes explains container registry →

Kubernetes for Developers

A container repository is a storage location that stores and distributes container images identified by image names and tags.

How it is used
Supplies Kubernetes with container images that were built locally and must run in a cloud cluster.
How deep it goes
Explains storage, visibility, authentication, provider choice, tagging, and pushing, but stops short of registry internals.
Examples
Uses Docker Hub, Artifact Registry, tagged timeserver images, docker push, and versioned repository paths.
What you can do after
Build and upload a versioned container image that Kubernetes can fetch for deployment.

Read how Kubernetes for Developers explains container registry →

Kubernetes in Action, Second Edition

A container registry is a repository service that stores and distributes container images to authorized clients.

How it is used
Distributes container images between developers, computers, and application environments.
How deep it goes
Explains storage, public versus private access, pushing, pulling, and container creation without detailing registry internals.
Examples
Uses the build, push, pull, and run flow across two Docker-enabled computers.
What you can do after
Operate Docker image distribution by pushing images to a registry and pulling them to create containers.

Read how Kubernetes in Action, Second Edition explains container registry →

Google Anthos in Action

A Docker registry is a service that stores and distributes Docker container images.

How it is used
Stores and distributes container images while supporting vulnerability scanning and cluster admission controls.
How deep it goes
Explains API enablement, repository creation, regional authentication, and registry admission testing, but defers detailed image tagging and pushing.
Examples
Uses gcloud repository commands, regional Docker authentication, approved-registry constraints, and rejected or dry-run Kubernetes workloads.
What you can do after
Operate/configure a GCP Docker repository and assess registry restrictions with Gatekeeper policies.

Read how Google Anthos in Action explains container registry →

Spring in Action, Sixth Edition

A container registry is a service that stores and distributes container images.

How it is used
Deploys a built Spring Boot container image by naming it for a DockerHub repository and pushing it there.
How deep it goes
Explains image tags, Maven and Gradle configuration, and pushing, but does not detail registry internals.
Examples
Uses the tacocloud repository, versioned image tags, Spring Boot build commands, and docker push.
What you can do after
Operate/configure a Spring Boot build to create and publish a repository-tagged Docker image.

Read how Spring in Action, Sixth Edition explains container registry →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.