-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rd.live.overlay.overlayfs=1 is broken on Fedora 39 LiveOS #2645
Comments
Food for thoughts: couldn't it be related with SELinux rules because of the folders where /run/overlayfs stores all modified files and directories after thoses unpacked from squashfs in the live boot ? I found this thread in Fedora Discussion and this and that bugzilla report Can't be sure if it helps or not, it is well beyond my understanding I didn't use any of the livecd-tools to reproduce this issue. The Fedora 39 LiveOS was directly written into an usb using following command Then the usb drive was booted and it's grub.cfg modified according to my description above FYI: livecd-tools can't be used as of Fedora 39 and since Fedora 35+ because the structure of the .iso files has been changed and an appropriate release still needs to be available from the official Fedora repos. see this issues livecd-tools/livecd-tools#244 and livecd-tools/livecd-tools#253 in livecd-tools repository |
The 2 problems you identified at the top are fixed in an update of Fedora 39 such as in the live-respin, https://dl.fedoraproject.org/pub/alt/live-respins/F39-WORK-x86_64-LIVE-20240401.iso The dracut documentation #Booting live images is incomplete. It should rather say: SquashFS (read-only) base filesystem image
Using one of these technologies, the system will provide a writable overlay for With the original Device-mapper snapshot overlay, users must be careful to When rd.live.overlay= is not specified for persistent overlay storage, or Even with large Device-mapper overlay files for write space, the available root This shortage could be remedied by building the root filesystem with more When the rd.live.overlay.overlayfs option is specified or when For non-persistent OverlayFS overlays, the Cross reference link dracut-ng/dracut-ng#137 |
@FGrose : thanks for your reply . Which kernel command line parameter is needed to activate on a Fedora Worsktation Live .ISO, the "Device-mapper snapshot based non-persistent overlays":
Regarding live-respins
Are live-respins natively corrected for I'll try soon |
@FGrose Thanks for updating the man page. What are the minimal kernel command line parameters to activate (on a freshly created Fedora 40beta Workstation Live USB):
|
Describe the bug
A clear and concise description of what the error is.
rd.live.overlay.overlayfs=1
is supposed to provide a non-persistent (i.e. deleted after reboot of Live Image) and temporary storage in RAM at/run/overlayfs
which is by default 32GiB unless another parameter is supplied :rd.live.overlay.size=<size_MiB>
. See dracut documentation #Booting live imagesUsing
rd.live.overlay.overlayfs=1
as kernel command line parameter has two issuessudo dmesg | grep overlayfs
includes an error:[ 13.317280] overlayfs: failed to resolve '/run/overlayfs': -2
Installing any rpm package once Fedora 39 LiveOS is running, results with the same errors
error: lsetfilecon: (33 /usr/bin/make-dummy-cert;66130180, system_u:object_r:bin_t:s0) Permission denied
error: Plugin selinux: hook fsm_file_prepare failed
[...]
Error unpacking rpm package
Failed:
Error: Transaction failed
Below an example with
openssl
Distribution used
Which distribution was this behaviour seen in?
Fedora 39 LiveOS
Dracut version
Which dracut version was this behaviour seen in?
Fedora 39 dracut-059-16.fc39
Init system
Which init system is being used?
systemd
To Reproduce
Steps or code to reproduce the behavior.
Insert alongside your kernel command line parameter on Fedora 39 Live ISO (for example in a
grub.cfg
menuentry)rd.live.overlay.overlayfs=1
after the parameterrd.live.image
Expected behavior
A clear and concise description of what you expected to happen.
We should have with this parameter :
a root live filesystem with 32GiB of available space instead of 4.9G is used and 1.5G is available space out of a total size of 6.4G
the ability to install rpm packages with
sudo dnf install <package>
until the available RAM is depletedAdditional context
Add any other context you like about the problem here.
a. Users of Fedora Linux have been reporting related bugs here: https://discussion.fedoraproject.org/t/fedora-liveos-root-system-and-available-ram/82531/1
CC @gregory-lee-bartholomew
(Cherry-picked commit from #2604)
b. The Booting Live Images documentation section could need be more "verbose" with more explanations, examples, use-cases. IMHO
The text was updated successfully, but these errors were encountered: