A container image packages an application, its user-mode system, and runtime metadata into an artifact used to deploy containers. Images can be stored in registries and deployed across Kubernetes-conformant environments. section 15.3.2 section 13.5.2
Operationally, a container image supports several responsibilities:
- Carry application files, user services, and required persistent-volume definitions produced during VM migration. section 15.3.2
- Separate reusable layers, such as a migration runtime and a captured system-image layer, so updates can be maintained incrementally. section 15.6
- Move through a build-and-deploy workflow: build or pull the image, apply the target registry tag, push it, and deploy it. section 13.5.2 section 15.4.4
- Support postmigration operations including software updates, configuration changes, security patches, and rolling application updates. section 15.6
Tag and publish an image
Pull CentOS 8, tag it for Artifact Registry using the required location, project, repository, and image naming convention, then push the tagged image. section 13.5.2
docker tag centos:8 us-east4-docker.pkg.dev/test1-236415/docker-registry/centos:8
Inspect the concrete registry naming pattern used when tagging an image for Google Cloud. section 13.5.2
