A tag such as site:2 makes an image reference easy to read. A publisher can move a tag when it pushes a replacement. To identify exact image content, record its digest, a value calculated from the referenced content.
Deployment · Lesson 2
Image Versions
Learn to distinguish an image tag from a digest and compare the exact images two environments use.
Reading a Tag
Imagine a registry shows these records on two different days. These abbreviated digest values are illustrative and cannot be used to pull an image.
Monday site:2 sha256:a1b2…
Tuesday site:2 sha256:c3d4…
The same tag now points to different content. A machine that pulled on Monday may still use the older image.
Both environments report the tag site:2. What would show which image each actually pulled?
Reading a Digest Reference
An image reference can use an @ followed by the full digest. This asks the registry for that exact object. Use the full digest from the registry or build record. Shortened display values are useful in examples and insufficient to retrieve the image.
Which form selects a particular registry object?
Comparing Like for Like
An image name can point to a list of builds for different machine types, or to one image for a specific platform. When comparing what two hosts actually run, record their platform and compare the relevant platform-specific image references. Keep the original full reference in the release record.
A release supports both arm64 and amd64. Which comparison is useful when checking two amd64 hosts?
Lesson complete
You finished Image Versions
You can now trace an exact image beyond its friendly tag.
Explain why the same tag can point to different content.
Recognize a full digest reference.
Compare the correct platform-specific image.
Keep your learning progress
Create a free account to save this lesson and continue learning on any device.
Create a free account