On Tue, Jun 4, 2019 at 8:13 AM QingFeng Hao <haoqf(a)linux.vnet.ibm.com> wrote:
According to the link https://coreos.com/ignition/docs/latest/boot-process.html
only takes effect at the first boot.
But we want to make it effect later if we missed something in the first boot, or we want
to debug ignition.
If you missed something, it's safer to just fix your Ignition config
and reprovision the machine from scratch. Ignition has non-idempotent
bits in it, for example the `append` and `overwrite` keys.
That said, if you really do want to have Ignition rerun for debugging
purposes, in FCOS/RHCOS you can use `ignition.firstboot=1`. This gets
picked up here:
The docs at https://coreos.com/
are generally for Container Linux,
though some things do apply to RHCOS/FCOS (e.g. the Ignition v2.2
specification for RHCOS). I don't think we have this specific change
documented somewhere else yet.
> Thanks a lot!
> QingFeng Hao
> CoreOS mailing list -- coreos(a)lists.fedoraproject.org
> To unsubscribe send an email to coreos-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: