-
Notifications
You must be signed in to change notification settings - Fork 70
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
Injecting configuration files after installation, before first boot #531
Comments
See #267 for a more convenient method. We are indeed in a relatively inconsistent situation where e.g. Anaconda allows this, but bootc-image-builder and bootc install don't in any kind of direct way; the above PR helps.
Yes, agreed. |
I gathered there was divergent functionality here and this was not really supported now. What is the present day workaround?
As for a workaround, should I just dump stuff into |
It would be a much more pleasant experience if |
It's almost certainly because you have a distinct |
This is exactly what the issue was. The documentation for |
How does one inject a configuration file post
bootc install
but before the first system boot? A customized/etc/fstab
is a good example or perhaps some systemd mount units. With a non-ostree system when the installation chroot is setup this is a straightforward copy operation.bootc
should document this process a bit better or provide a more convenient method as it will be a common need to drop some configuration files in place post install but before the system boots for the first time. Not everyone will want to adopt ignition to do these tasks.The text was updated successfully, but these errors were encountered: