[06:03] <cpaelzer> Church: you'd use it like any other cloud config, it just has to start with a different header as outlined https://cloudinit.readthedocs.io/en/latest/topics/format.html#user-data-script
[06:04] <cpaelzer> Church: so if all you want to do is to create a nocloud image bsaed on that, then yes passing it to cloud-localds should do it
[07:46] <Church> Nod, got it. A follow up question, what's a good way to execute a user data based script at the end of the cloud init process? Attempting to debug why user data on AWS isn't executing correctly so I'm attempting a nocloud image to debug locally.
[07:47] <Church> Thinking that my first command in the script to `cloud-init status --wait` isn't working correctly. Nor is waiting for the /var/lib/cloud/instance/data/boot-finished file to exist before continuing my user data script working either.
[12:56] <holtgrewe> Hello. I want to bootstrap a RockyLinux based machine with cloud-init. I have the following in /var/lib/cloud/instance/cloud-config.txt. https://pastebin.com/ZEMfmqnN However, eth0 and eth1 are configured with DHCP. Other configuration such as SSH host keys are written correctly.
[12:57] <holtgrewe> My VM is launched from OpenStack. Am I overlooking something? Why is my network configuration not applied from /var/lib/cloud/instance/cloud-config.txt?
[13:03] <holtgrewe> Hm, maybe this configuration must come from /etc/cloud/cloud.cfg{,.d/*} and not from the user-data...
[13:13] <holtgrewe> Yes, that is the case. https://stackoverflow.com/a/58368766/84349
[15:15] <martti> hello everyone