State of affairs summary:
Btrfs Cloud images will boot and function as normal even on hosts that do not support btrfs (e.g. RHEL). Resizing is also not impacted, as that's generally handled via cloud-init.
A standalone Fedora-built libguestfs container will allow image access regardless of host kernel support. See: https://bugzilla.redhat.com/show_bug.cgi?id=1970071 https://src.fedoraproject.org/container/libguestfs .
grub2-mount can provide read-only support via GRUB's btrfs.mod and zstd.mod. See: https://bugzilla.redhat.com/show_bug.cgi?id=1970538 https://bugzilla.redhat.com/show_bug.cgi?id=1972386 https://git.centos.org/rpms/grub2/pull-request/1 https://github.com/rhboot/grub2/pull/86.
btrfs-fuse confirmed as feasible, design work pending
Detailed version
Should the Cloud landing page, where these images are located, contain a note for RHEL/CentOS users, letting them know they can use these images, and point them to e.g. a quickdoc laying out the above options and How To?
Qu Wenruo is working on a read-only FUSE implementation, which @dcavalca has packaged up for Fedora. When it gets to its first stable release, I imagine we can ship it to RHEL/CentOS in EPEL to neatly solve this problem.
Metadata Update from @ngompa: - Issue assigned to dcavalca - Issue set to the milestone: Fedora 36 (was: Fedora 35)
This has now landed in EPEL 8: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-7520d38390
Issue status updated to: Closed (was: Open) Issue close_status updated to: Fixed
Login to comment on this ticket.