Building image fails on btrfs due to mkfs.erofs xattr limitation
Unless extended attributes are disabled (with -x-1), mkfs.erofs fails when the source is a BTRFS filesystem. This prevents the Spectrum image from being built. Using -x-1 seems to produce a working installer, though I only smoke tested it (by trying the example VMs). -- Sincerely, Demi Marie Obenour (she/her/hers)
Demi Marie Obenour <demiobenour@gmail.com> writes:
Unless extended attributes are disabled (with -x-1), mkfs.erofs fails when the source is a BTRFS filesystem. This prevents the Spectrum image from being built. Using -x-1 seems to produce a working installer, though I only smoke tested it (by trying the example VMs).
That's odd — I frequently run mkfs.erofs on btrfs. Could it be some difference in our filesystem/mount options? Could it just be that my files don't have extended attributes and yours do (SELinux)?
On 7/5/25 04:52, Alyssa Ross wrote:
Demi Marie Obenour <demiobenour@gmail.com> writes:
Unless extended attributes are disabled (with -x-1), mkfs.erofs fails when the source is a BTRFS filesystem. This prevents the Spectrum image from being built. Using -x-1 seems to produce a working installer, though I only smoke tested it (by trying the example VMs).
That's odd — I frequently run mkfs.erofs on btrfs. Could it be some difference in our filesystem/mount options? Could it just be that my files don't have extended attributes and yours do (SELinux)?
Yeah, it might well be SELinux. Spectrum should still build on systems with SELinux enabled, though. Does Spectrum use extended attributes? If not, would it make sense to disable them with -x-1? In the future, SELinux on the host will require fixing this, but for now it's better to fix the build error. -- Sincerely, Demi Marie Obenour (she/her/hers)
Demi Marie Obenour <demiobenour@gmail.com> writes:
On 7/5/25 04:52, Alyssa Ross wrote:
Demi Marie Obenour <demiobenour@gmail.com> writes:
Unless extended attributes are disabled (with -x-1), mkfs.erofs fails when the source is a BTRFS filesystem. This prevents the Spectrum image from being built. Using -x-1 seems to produce a working installer, though I only smoke tested it (by trying the example VMs).
That's odd — I frequently run mkfs.erofs on btrfs. Could it be some difference in our filesystem/mount options? Could it just be that my files don't have extended attributes and yours do (SELinux)?
Yeah, it might well be SELinux. Spectrum should still build on systems with SELinux enabled, though. Does Spectrum use extended attributes? If not, would it make sense to disable them with -x-1? In the future, SELinux on the host will require fixing this, but for now it's better to fix the build error.
Yes, of course. I just wanted to understand why it might be happening for you and not to me. Disabling extended attributes in mkfs.erofs sounds like the right thing to do.
participants (2)
-
Alyssa Ross -
Demi Marie Obenour