-
Notifications
You must be signed in to change notification settings - Fork 243
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
Allow Ignition to run shell commands #909
Comments
Ignition configs are declarative and shell scripts are not. However, you can use Ignition to write a one-shot systemd unit that has |
I understand the sentiment behind that statement, but it disregards the fact that Ignition simply cannot do many things. Provisioning frameworks such as ansible and chef provide mechanisms for installing packages, manage system services and a lot more. Yet, Ignition is supposed to be the provisioning tool for coreos but is lacking basic abilities to actually properly provision a host. Delegating provisioning by hacking a systemd unit is not only counter-intuitive but even completely defeats the purpose of a provisioning tool. There will be no feedback on whether the provisioning was actually successful. |
You get feedback from Being able to run completely independent scripts in separate systemd units also makes it easier to debug and follow progress. E.g. OCP helpfully prints this when you log in during installation. As far as marking provisioning as successful, Ignition itself will fail if it couldn't provision the machine. In the real root, we have some design work going on in coreos/fedora-coreos-tracker#47 to verify that the machine actually came up "successfully", for a user-customizable definition of what successful means. |
One bridge we could make though is to have an |
Feature Request
I want Ignition to overlay packages with
rpm-ostree install
to install cockpit in addition to my containers that are setup by systemd units.Because of Ignition's goal to be distro agnostic, a feature to directly allow overlay packages in the config will not be accepted. How about an option to run any shell commands be added instead? That would allow any modifications to be done automatically, without running a separate shell script on first boot.
The text was updated successfully, but these errors were encountered: