-
Bug
-
Resolution: Won't Do
-
Undefined
-
None
-
rhel-9.6
-
No
-
None
-
rhel-anaconda
-
None
-
False
-
False
-
-
No
-
None
-
None
-
None
-
Unspecified Release Note Type - Unknown
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
Image mode kickstart installation using a locally-stored (embedded in the boot ISO) OCI archive container image fails due to insufficient space in the root filesystem (/var/tmp in the log):
17:34:53,747 INF program: Running... ostree container image deploy --sysroot=/mnt/sysimage --image=/run/install/repo/oci.img --transport=oci-archive --no-signature-verification 17:34:58,348 INF program: error: Performing deployment: Creating importer: failed to invoke method OpenImage: failed to invoke method OpenImage: creating temp directory: untarring file "/var/tmp/container_images_oci2635607030": write /var/tmp/container_images_oci2635607030/blobs/sha256/9f722a0378ba668fec318efc869a77d0150e57c733ed723cff5a965ea63e8cc0: no space left on device 17:34:58,349 DBG program: Return code: 1
Deployment of the OCI archive image works on RHEL-9.5 with 2.5 GiB of RAM and RHEL-9.4 with 2 GiB of RAM, however on RHEL-9.6, it fails no matter what amount of memory is available.
In my case my embedded image occupied 823 MiB on RHEL-9.4 and 926 MiB on RHEL-9.6; root filesystem had 956 MiB available on RHEL-9.4 and 740 MiB on RHEL-9.6.
What is the impact of this issue to you?
It's not possible to deploy a bootc container image (embedded in the boot ISO).
Please provide the package NVR for which the bug is seen:
anaconda-34.25.5.16-1.el9
How reproducible is this bug?:
Always.
Steps to reproduce
- Pull and save the bootc container image:
podman pull $rhel-bootc-image
podman save --format oci-archive -o oci.img - Embed it into a RHEL-9.6 boot ISO:
mkksiso -a oci.img original-boot.iso new-boot.iso - Prepare a kickstart file using the embedded OCI image:
...
ostreecontainer --no-signature-verification --transport=oci-archive --url=/run/install/repo/oci.img - Start system installation using the prepared ISO and kickstart.
Expected results
Installation is successful.
Actual results
Installation fails due to insufficient space on the root filesystem.