Syarif's Blog

Guided Exercise: Container Image Identity and Tags

Syarif's photo
Syarif
·

11 min read

Update an application by changing its deployment to reference a newer image tag, and find the hashes of the old and new application images.

Outcomes

You should be able to inspect container images, list images of containers that run on compute nodes, and deploy applications by using image tags or SHA IDs.

As the student user on the workstation machine, use the lab command to prepare your system for this exercise.

This command ensures that all resources are available for this exercise. It also creates the updates-ids project and the /home/student/DO180/labs/updates-ids/resources.txt file. The resources.txt file contains the name of the images and some commands that you use during the exercise. You can use the file to copy and paste these image names and commands.

[student@workstation ~]$ lab start updates-ids

Procedure 7.1. Instructions

  1. Log in to the OpenShift cluster as the developer user with the developer password. Use the updates-ids project.

    1. Log in to the OpenShift cluster.

       [student@workstation ~]$ oc login -u developer -p developer \
   https://api.ocp4.example.com:6443
 Login successful.
 ...output omitted...

    2. Set the updates-ids project as the active project.

       [student@workstation ~]$ oc project updates-ids
 ...output omitted...

  2. Inspect the two versions of the registry.ocp4.example.com:8443/ubi8/httpd-24 image from the classroom container registry. The classroom setup copied that image from the Red Hat Ecosystem Catalog. The original image is registry.access.redhat.com/ubi8/httpd-24.

    1. Use the oc image info command to inspect the image version that the 1-209 tag references. Notice the unique SHA ID that identifies the image version.

      NOTE

      To improve readability, the instructions truncate the SHA-256 strings.

      On your system, the commands return the full SHA-256 strings. Also, you must type the full SHA-256 string, to provide such a parameter to a command.

       [student@workstation ~]$ oc image info \
   registry.ocp4.example.com:8443/ubi8/httpd-24:1-209
 Name:          registry.ocp4.example.com:8443/ubi8/httpd-24:1-209
 Digest:        sha256:b1e3...f876
 ...output omitted...

    2. Inspect the image version that the 1-215 tag references. Notice that the SHA ID, or digest, differs from the preceding image version.

       [student@workstation ~]$ oc image info \
   registry.ocp4.example.com:8443/ubi8/httpd-24:1-215
 Name:          registry.ocp4.example.com:8443/ubi8/httpd-24:1-215
 Digest:        sha256:91ad...fd83
 ...output omitted...

    3. For inspecting images, you can also use the skopeo inspect command. The output format differs from the oc image info command, although both commands report similar data.

      Log in to the registry as the developer user with the developer password by using the skopeo login command. Then, use the skopeo inspect command to inspect the 1-215 image tag.

       [student@workstation ~]$ skopeo login registry.ocp4.example.com:8443 -u developer
 Password:
 Login Succeeded!

       [student@workstation ~]$ skopeo inspect \
   docker://registry.ocp4.example.com:8443/ubi8/httpd-24:1-215
 {
     "Name": "registry.ocp4.example.com:8443/ubi8/httpd-24",
     "Digest": "sha256:91ad...fd83",
     "RepoTags": [
         "1-209",
         "1-215"
     ],
 ...output omitted...
 }

      The skopeo inspect command also shows other existing image tags.

  3. Deploy an application from the image version that the 1-209 tag references.

    1. Use the oc create deployment command to deploy the application. Set the name of the deployment to httpd1. Ignore the warning message.

       [student@workstation ~]$ oc create deployment httpd1 \
   --image registry.ocp4.example.com:8443/ubi8/httpd-24:1-209
 Warning: would violate PodSecurity "restricted:v1.24":
 ...output omitted...
 deployment.apps/httpd1 created

    2. Wait for the pod to start, and then retrieve the name of the cluster node that runs it. You might have to rerun the command several times for the pod to report a Running status. The name of the pod on your system probably differs.

       [student@workstation ~]$ oc get pods -o wide
 NAME                     READY  STATUS   RESTARTS  AGE  IP          NODE     ...
 httpd1-6dff796d99-pm2x6  1/1    Running  0         19s  10.8.0.104  master01 ...

    3. Retrieve the name of the container that is running inside the pod. The crictl ps command that you run in a following step takes the container name as an argument.

       [student@workstation ~]$ oc get deployment httpd1 -o wide
 NAME     READY   UP-TO-DATE   AVAILABLE   AGE     CONTAINERS  ...
 httpd1   1/1     1            1           1m10s   httpd-24    ...

  4. Access the cluster node and then retrieve the image that the container is using.

    1. You must log in as the admin user to access the cluster node. Use the redhatocp password.

       [student@workstation ~]$ oc login -u admin -p redhatocp
 Login successful.
 ...output omitted...

    2. Use the oc debug node command to access the cluster node.

       [student@workstation ~]$ oc debug node/master01
 Temporary namespace openshift-debug-flz4d is created for debugging node...
 Starting pod/master01-debug ...
 To use host binaries, run `chroot /host`
 Pod IP: 192.168.50.10
 If you don't see a command prompt, try pressing enter.

    3. In the remote shell, run the chroot /host command.

       sh-4.4# chroot /host
 sh-4.4#

    4. Use the crictl ps command to confirm that the httpd-24 container is running. Add the -o yaml option to display the container details in YAML format.

       sh-4.4# crictl ps --name httpd-24 -o yaml
 containers:
 - annotations:
 ...output omitted...
   image:
     annotations: {}
     image: registry.ocp4.example.com:8443/ubi8/httpd-24@sha256:b1e3...f876
   imageRef: registry.ocp4.example.com:8443/ubi8/httpd-24@sha256:b1e3...f876
   labels:
 ...output omitted...
   state: CONTAINER_RUNNING

      Notice that the command refers to the image by its SHA ID, and not by the tag that you specified when you created the deployment resource.

    5. Use the crictl images command to list the locally available images on the node. The registry.ocp4.example.com:8443/ubi8/httpd-24:1-209 is in that list, because the local container engine pulled it when you deployed the httpd1 application.

      NOTE

      The IMAGE ID column displays the local image identifier that the container engine assigns to the image. This identifier is not related to the SHA image ID that the container registry assigned to the image.

      Most crictl commands, such as crictl images or crictl rmi, accept a local image identifier instead of the full image name. For example, you can run the crictl images 8ee59251acc93 command as a short version of the crictl images registry.ocp4.example.com:8443/ubi8/httpd-24:1-209 command.

       sh-4.4# crictl images
 IMAGE                                           TAG     IMAGE ID           SIZE
 quay.io/openshift-release-dev/ocp-release       <none>  d52324cb88017      444MB
 quay.io/openshift-release-dev/ocp-v4.0-art-dev  <none>  22e6e45df32af      468MB
 quay.io/openshift-release-dev/ocp-v4.0-art-dev  <none>  e798432938c49      503MB
 quay.io/openshift-release-dev/ocp-v4.0-art-dev  <none>  3ca084e53b321      873MB
 ...output omitted...
 registry.ocp4.example.com:8443/ubi8/httpd-24    1-209   8ee59251acc93      461MB
 ...output omitted...

    6. The preceding crictl images command does not display the SHA image IDs by default. Rerun the command and add the --digests option to display the SHA IDs. Also add the local image ID to the command to limit the output to the registry.ocp4.example.com:8443/ubi8/httpd-24:1-209 image.

      The command reports only the first characters of the SHA image ID. These characters match the SHA ID of the image that the httpd-24 container is using. Therefore, the httpd-24 container is using the expected image.

       sh-4.4# crictl images --digests 8ee59251acc93
 IMAGE                                        TAG   DIGEST        IMAGE ID      ...
 registry.ocp4.example.com:8443/ubi8/httpd-24 1-209 b1e3c572516d1 8ee59251acc93 ...

    7. Disconnect from the cluster node.

       sh-4.4# exit
 exit
 sh-4.4# exit
 exit

 Removing debug pod ...
 Temporary namespace openshift-debug-flz4d was removed.
 [student@workstation ~]$

  5. Log in as the developer user and then deploy another application by using the SHA ID of the image as the digest.

    1. Log in to the OpenShift cluster as the developer user.

       [student@workstation ~]$ oc login -u developer -p developer
 Login successful.
 ...output omitted...

    2. Rerun the oc image info command to retrieve the SHA ID of the image version that the 1-209 tag references. Specify the JSON format for the command output. Parse the JSON output with the jq -r command to retrieve the value of the .digest object. Export the SHA ID as the $IMAGE environment variable.

       [student@workstation ~]$ oc image info \
   registry.ocp4.example.com:8443/ubi8/httpd-24:1-209 -o json | \
   jq -r .digest
 sha256:b1e3...f876

       [student@workstation ~]$ IMAGE=sha256:b1e3...f876

    3. Use the oc create deployment command to deploy the application. Set the name of the deployment to httpd2. Ignore the warning message.

       [student@workstation ~]$ oc create deployment httpd2 \
   --image registry.ocp4.example.com:8443/ubi8/httpd-24@$IMAGE
 Warning: would violate PodSecurity "restricted:v1.24":
 ...output omitted...
 deployment.apps/httpd2 created

    4. Confirm that the new deployment refers to the image version by its SHA ID.

       [student@workstation ~]$ oc get deployment httpd2 -o wide
 NAME     READY  ...  CONTAINERS   IMAGES ...
 httpd2   1/1    ...  httpd-24     registry.../ubi8/httpd-24@sha256:b1e3...f876 ...

  6. Update the httpd2 application by using a more recent image version.

    1. In the httpd2 deployment, update the httpd-24 container to use the image version that the 1-215 tag references. Ignore the warning message.

       [student@workstation ~]$ oc set image deployment/httpd2 \
   httpd-24=registry.ocp4.example.com:8443/ubi8/httpd-24:1-215
 Warning: would violate PodSecurity "restricted:v1.24":
 ...output omitted...
 deployment.apps/httpd2 image updated

    2. Confirm that the deployment refers to the new image version.

       [student@workstation ~]$ oc get deployment httpd2 -o wide
 NAME     READY   ...    IMAGES ...
 httpd2   1/1     ...    registry.ocp4.example.com:8443/ubi8/httpd-24:1-215 ...

    3. Confirm that the deployment finished redeploying the pod. You might have to rerun the command several times for the pod to report a Running status. The pod names probably differ on your system.

       [student@workstation ~]$ oc get pods
 NAME                      READY   STATUS    RESTARTS   AGE
 httpd1-6dff796d99-pm2x6   1/1     Running   0          118m
 httpd2-998d9b9b9-5859j    1/1     Running   0          21s

    4. Inspect the pod to confirm that the container is using the new image. Replace the pod name with your own from the previous step.

       [student@workstation ~]$ oc get pod httpd2-998d9b9b9-5859j \
   -o jsonpath='{.spec.containers[0].image}{"\n"}'
 registry.ocp4.example.com:8443/ubi8/httpd-24:1-215

  7. Add the latest tag to the image version that the 1-209 tag already references. Deploy an application from the image with the latest tag.

    1. Use the skopeo login command to log in to the classroom container registry as the developer user. Use developer for the password.

       [student@workstation ~]$ skopeo login -u developer -p developer \
   registry.ocp4.example.com:8443
 Login Succeeded!

    2. Use the skopeo copy command to add the latest tag to the image.

       [student@workstation ~]$ skopeo copy \
   docker://registry.ocp4.example.com:8443/ubi8/httpd-24:1-209 \
   docker://registry.ocp4.example.com:8443/ubi8/httpd-24:latest
 Getting image source signatures
 ...output omitted...
 Writing manifest to image destination
 Storing signatures

    3. Use the oc image info command to confirm that both tags refer to the same image. The two commands report the same SHA image ID, which indicates that the tags point to the same image version.

       [student@workstation ~]$ oc image info \
   registry.ocp4.example.com:8443/ubi8/httpd-24:1-209
 Name:          registry.ocp4.example.com:8443/ubi8/httpd-24:1-209
 Digest:        sha256:b1e3...f876
 ...output omitted...

       [student@workstation ~]$ oc image info \
   registry.ocp4.example.com:8443/ubi8/httpd-24:latest
 Name:          registry.ocp4.example.com:8443/ubi8/httpd-24:latest
 Digest:        sha256:b1e3...f876
 ...output omitted...

    4. Use the oc create deployment command to deploy another application. Set the name of the deployment to httpd3. To confirm that by default the command selects the latest tag, do not provide the tag part in the image name. Ignore the warning message.

       [student@workstation ~]$ oc create deployment httpd3 \
   --image registry.ocp4.example.com:8443/ubi8/httpd-24
 Warning: would violate PodSecurity "restricted:v1.24":
 ...output omitted...
 deployment.apps/httpd3 created

    5. Confirm that the pod is running. You might have to rerun the command several times for the pod to report a Running status. The pod names probably differ on your system.

       [student@workstation ~]$ oc get pods
 NAME                      READY   STATUS    RESTARTS   AGE
 httpd1-6dff796d99-pm2x6   1/1     Running   0          150m
 httpd2-998d9b9b9-5859j    1/1     Running   0          32m
 httpd3-85b978d758-fvqdr   1/1     Running   0          42s

    6. Confirm that the pod is using the expected image. Notice that the SHA image ID corresponds to the image that the 1-209 tag references. You retrieved that SHA image ID in a preceding step when you ran the oc image info command.

       [student@workstation ~]$ oc describe pod httpd3-85b978d758-fvqdr
 ...output omitted...
 Containers:
   httpd-24:
     Container ID: cri-o://2cee...3a68
     Image:        registry.ocp4.example.com:8443/ubi8/httpd-24
     Image ID:     registry.ocp4.example.com:8443/ubi8/httpd-24@sha256:b1e3...f876
 ...output omitted...

  8. Assign the latest tag to a different image version. This operation simulates a developer who pushes a new version of an image and assigns the latest tag to that new image version.

    1. Use the skopeo copy command to add the latest tag to the image version that the 1-215 tag already references. The command automatically removes the latest tag from the earlier image.

       [student@workstation ~]$ skopeo copy \
   docker://registry.ocp4.example.com:8443/ubi8/httpd-24:1-215 \
   docker://registry.ocp4.example.com:8443/ubi8/httpd-24:latest
 Getting image source signatures
 ...output omitted...
 Writing manifest to image destination
 Storing signatures

    2. Log out from the classroom container registry.

       [student@workstation ~]$ skopeo logout registry.ocp4.example.com:8443
 Removed login credentials for registry.ocp4.example.com:8443

    3. Even though the latest tag is now referencing a different image version, OpenShift does not redeploy the pods that are running with the previous image version.

      Rerun the oc describe pod command to confirm that the pod still uses the preceding image.

       [student@workstation ~]$ oc describe pod httpd3-85b978d758-fvqdr
 ...output omitted...
 Containers:
   httpd-24:
     Container ID: cri-o://2cee...3a68
     Image:        registry.ocp4.example.com:8443/ubi8/httpd-24
     Image ID:     registry.ocp4.example.com:8443/ubi8/httpd-24@sha256:b1e3...f876
 ...output omitted...

  9. Scale the httpd3 deployment to two pods.

    1. Use the oc scale command to add a new pod to the deployment.

       [student@workstation ~]$ oc scale deployment/httpd3 --replicas 2
 deployment.apps/httpd3 scaled

    2. List the pods to confirm that two pods are running for the httpd3 deployment. The pod names probably differ on your system.

       [student@workstation ~]$ oc get pods
 httpd1-6dff796d99-pm2x6   1/1     Running   0          75m
 httpd2-998d9b9b9-5859j    1/1     Running   0          30m
 httpd3-85b978d758-f98jh   1/1     Running   0          54s
 httpd3-85b978d758-fvqdr   1/1     Running   0          11m

    3. Retrieve the SHA image ID for the pod that the deployment initially created. The ID did not change. The container is still using the original image version.

       [student@workstation ~]$ oc describe pod httpd3-85b978d758-fvqdr
 ...output omitted...
 Containers:
   httpd-24:
     Container ID: cri-o://2cee...3a68
     Image:        registry.ocp4.example.com:8443/ubi8/httpd-24
     Image ID:     registry.ocp4.example.com:8443/ubi8/httpd-24@sha256:b1e3...f876
 ...output omitted...

    4. Retrieve the SHA image ID for the additional pod. Notice that the ID is different. The additional pod is using the image that the latest tag is currently referencing.

       [student@workstation ~]$ oc describe pod httpd3-85b978d758-f98jh
 ...output omitted...
 Containers:
   httpd-24:
     Container ID: cri-o://d254...c893
     Image:        registry.ocp4.example.com:8443/ubi8/httpd-24
     Image ID:     registry.ocp4.example.com:8443/ubi8/httpd-24@sha256:91ad...fd83
 ...output omitted...

      The state of the deployment is inconsistent. The two replicated pods use a different image version. Consequently, the scaled application might not behave correctly. Red Hat recommends that you use a less volatile tag than latest in production environments, or that you tightly control the tag assignments in your container registry.

Finish

On the workstation machine, use the lab command to complete this exercise. This step is important to ensure that resources from previous exercises do not impact upcoming exercises.

[student@workstation ~]$ lab finish updates-ids
openshift