-
Notifications
You must be signed in to change notification settings - Fork 88
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
fstab cleanup of /
does not work
#971
Comments
What generated that The reason we don't change that fstab line today is it already contains the Hmm, I'm guessing this didn't come from Anaconda, but I did find osbuild/bootc-image-builder@c609003 and while that wasn't wrong I really should have taken the next step and fixed it to not emit a fstab entry at all. |
Yes, I installed the system with an anaconda-iso produced by BIB. |
Umm so much technical debt in this area. AFAICS bib still uses this code for that case which is really suboptimal in so many ways because it uses the wrong filesystem type by default across different distros...not even honoring the bootc default filesystem. More generally default partitioning can differ by OS/distro or desired base image too...again ideally we support embedding this in the container image and in this embedded ISO case Anaconda could read that (ref rhinstaller/anaconda#5197 more generally). There is a big sub-thread here though that on the bootc side here we really do need to give guidance for people on how to use |
➡ #972 |
It looks like we regressed after commit d46b072 since the fstab cleanup does not work (anymore).
The
systemd-remount-fs.service
fails with/etc/fstab
includesThe text was updated successfully, but these errors were encountered: