On Wed, 2021-06-09 at 19:53 +0000, Zbigniew Jędrzejewski-Szmek wrote: > Yeah, I think we have to accept that there won't be any kernel support > in RHEL in a timeframe that matters for Fedora, and the RHEL host will > not be > able to mount the images natively. So the questions for me are: > 1. I this a problem in practice? I.e. how often do people need to use > Fedora > images for containers on RHEL hosts? > 2. What workaround can we put in place? Something in EPEL or dkms > module with > btrfs in a copr repo? I've put together a Fedora-based libguestfs container that should address some of these issues and allow accessing and manipulating btrfs filesystems even on RHEL hosts that do not support it. It's currently in review at https://bugzilla.redhat.com/show_bug.cgi?id=1970071 and I'd appreciate any feedback you might have there. In addition to this, we're exploring the possiblity of developing a userspace btrfs-fuse implementation by leveraging the existing logic in brtfsprogs, which could also provide an alternative access option. On the CentOS side, the Hyperscale SIG is working on a btrfs-enabled kernel for CentOS Stream: https://pagure.io/centos-sig-hyperscale/sig/issue/7 . There's also a kmods SIG currently being proposed (https://wiki.centos.org/SpecialInterestGroup/Kmods) that could be a place for distributing a btrfs module for RHEL / CentOS stock kernels for the time being. Cheers Davide _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
