kubevirt / containerized-data-importer / #6176

50%

push

travis-ci

importer: detect bootc/ostree-bootable container images (#4223)

* importer: detect bootc/ostree-bootable container images in registry imports

When a registry source image has OCI config labels `containers.bootc=1`
or `ostree.bootable=1`, the importer now detects it early (before layer
extraction) and returns a clear error indicating that bootc-to-disk
conversion is not yet implemented.

This is the first step toward full bootc import support, where CDI will
be able to convert bootc container images into bootable disk images
using `bootc install to-disk`, gated behind the new BootcImageImport
feature gate.

Signed-off-by: Vladik Romanovsky <vladikr@redhat.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* containerimage-server: detect bootc images in node-pull path

When using pullMethod: node, cdi-containerimage-server runs inside
the image filesystem and tries to serve files from /disk/. For bootc
images, /disk/ doesn't exist — the container IS the OS rootfs.

Check for /sysroot and /ostree directories (definitive ostree markers)
when the disk image directory is missing or invalid, and return a clear
error message instead of the opaque "Invalid container image".

Signed-off-by: Vladik Romanovsky <vladikr@redhat.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Signed-off-by: Vladik Romanovsky <vladikr@redhat.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

15 of 17 new or added lines in 2 files covered. (88.24%)

15166 of 30475 relevant lines covered (49.77%)

0.56 hits per line