With zfs 2.1.x, this happened automatically. Though unclear why, it no longer seems to occur when installing the zfs 2.2.x RPMs in a container build (it does still work automatically on a non image-based Fedora system).
Manually running depmod, as in this commit, ensures the 2.2.x kmods load as expected.
With zfs 2.1.x, this happened automatically. Though unclear why, it no longer seems to occur when installing the zfs 2.2.x RPMs in a container build (it does still work automatically on a non image-based Fedora system).
Manually running depmod, as in this commit, ensures the 2.2.x kmods load as expected.
Fixes: #88