Hello.
Let’s take an image of Fedora, Bootc, and Konflux that we intend to inspect.
‘podman search --no-trunc bootc | grep konflux’
Chosen image:
‘quay.io/konflux-fedora/bootc-tenant/fedora-bootc-rawhide-minimal’
Image referred to from now as ‘<image>’ in the command-lines that follow.
Sometimes images are tagged “latest” However, these images can introduce incompatible changes or create unexpected variations in the software deployment. Therefore, the ability to acquire the latest version of an image via Podman is primarily useful in non-production environments or for those experimenting exclusively with Podman tools. In production environments, such tagging is arguably bad practice.
note: establishing the validity of using such images in a production environment is irrelevant here.
The “latest” tag is not associated with the current images provided by the Fedora Project for bootc with Konflux. This can be seen with the following command when the default tag configuration is used in Podman:
‘skopeo inspect docker://<image>’
The output informs of an unknown manifest, which is expected. Consequently, this prevents Podman from acquiring an image with ‘podman pull ’ alone. Furthermore, Podman can no longer determine the appropriate architecture of the image to be pulled.
Therefore, we need in the following way to determine the tags that can be associated with our image.
‘podman search --list-tags --format={{.Tag}} ’
Revealed supported Linux hardware architectures: arm64, amd64, ppc64le, s390x.
In conclusion: the directory structure of the chosen image can be improved.
Optimisation suggestions along with their suitability:
- ‘
quay.io/konflux-fedora/bootc-tenant/<image_name>’
For non-architectural-specific and Git images. 'quay.io/konflux-fedora/bootc-tenant/<architecture>/<image_name>'
For architectural-specific images.