-
Notifications
You must be signed in to change notification settings - Fork 60
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
How to handle machine-specific config in early boot #464
Comments
/cc @dustymabe @cgwalters @jlebon Discussion from Dracut |
Note today if one enables the Now, it's certainly true that there isn't an exposed knob to regenerate the initramfs before an install today, but it'd likely work to mount the target root after
This is conflating the "bootetc copy" (your PR) with my proposed "just read /boot/etc/multipath.conf" though? |
No, this was in response to @jlebon concern of two sources of truth. If there are two |
FWIW, I started working on @cgwalters suggestion of a narrowly scoped source of specific configuration files. But I don't want to submit it until after we have made a decision here. |
To reply to
No, with the "targeted config" approach, there would only be Now, if client-side initramfs regeneration is enabled, since this PR landed we still shouldn't see the copy in the real root unless the user explicitly did Right? |
I think this is fixed by coreos/rpm-ostree#2170 now, so tentatively closing. That said, we'll likely want more sugaring on top on the OS integration side to make it transparent and easier to use. |
Moving dracutdevs/dracut#792 here to be respectful to Dracut upstream.
Axiom: Some devices require machine configuration before the OStree is mounted. This configuration is typically included during the generation of the initramfs.
In general, RHCOS users get their initramfs from Red Hat. For FCOS, user could regenerate if needed. We need a solution that works with both RHCOS and FCOS.
I have explored a number of options, each option have significant problems:
Then multipath, iSCSI and other complicated disk setups can't be supported by CoreOS -- that is the state of things today.
Can we decide on what path we want to take? Or do we say, tough luck? Is there some option I haven't considered?
The text was updated successfully, but these errors were encountered: