-
Bug
-
Resolution: Unresolved
-
Major
-
4.21
Description of problem:
When downloading microshift OCI container images to create an offline appliance, the resulting downloaded OCI container images for the sriov images is huge with 4.7G, compares to e.g. core 1.5G or multus only 154. It seems that multi-arch images are downloaded, tho only x86 or arm64 would be required.
Version-Release number of selected component (if applicable):
4.21
How reproducible:
Always
Steps to Reproduce:
1. Download the OCI continer images, following code snipped used to embedd container images into a bootc image, but not in the context of a Containerfile, simply on a shell command line (https://docs.redhat.com/en/documentation/red_hat_build_of_microshift/4.21/html/installing_with_image_mode_for_rhel/creating-a-fully-self-contained-bootc-image#microshift-embed-cont-images-bootc-image_microshift-install-bootc-physically-bound)
2. repeat this for microshift core (e.g. release-x86_64.json), multus (release-multus-x86_64.json) and sriov (release-sriov-x86_64.json) into different folder.
3.check the folder size
4.Compare the image digests for sriov x86 vs aarch using
# cd /usr/share/microshift/release/
# diff release-sriov-aarch64.json release-sriov-x86_64.json
Actual results:
images]# du -hs * 1.5G core 154M multus 4.7G sriov <<<<<< WAY TOOO BIG # diff release-sriov-aarch64.json release-sriov-x86_64.json # ^^^^^ NO difference in images????
Expected results:
sriov should be way smaller, and x86 vs. aarch release info should show differences.
Additional info: