So #AlmaLinux on the #raspberrypi4 is really nice. I installed #almalinuxkitten because I needed some features to manage #quadlets with #cockpit. Alma 10 was missing those.
Also the #cloudinit stuff is really nice. Preconfigure some stuff, booting and done.
Currently serving #pihole and #unboud in a #podman #pod on the pi.
More to come 😁
Oh great, I've literally spent days (over the span of 5 weeks) trying to get my cloud-init config running on an Ubuntu 26.04 LTS image on Scaleway.
My user-data file was available, it was parsable by cloud-init as valid when specifically asked to, it "just" not merged and processed my cloud-config.
Now I've done several rounds of debugging and never noticed that the Scaleway datasource was missing.
Downgraded to 24.04 and bang: it finally worked.
The speed-difference between #EC2Launch and #cloud-init is pretty stark. When I fire up a #Linux instance that has a #userData payload, doing:
8472
🌈 Kerblambuli 🦄
ferricoxidesleep $(( 60 * 2 )) ; ssh <USER>@<INSTANCE_ID>Is usually sufficient to get me a login. If I launch a Windows-based EC2, I usually have to do:sleep $(( 60 * 10 )) ; aws ssm start-session --target <INSTNCE_ID>Unless I want the dreaded "not available error". Worse, while two-minute pause for the cloud-init/Linux EC2 usually logs me in with the cloud-init content well underway, the #SSM login, after a ten-minute pause, usually has me arriving well before EC2Launch has even finished unpacking its data to start executing powershell scripts. It's like "dafuq is taking you so long??"A big limitation for #incus coming from #cloudinit: it is impossible to properly merge cloud-config keys between user-data and vendor-data. Even after setting merging rules, the user-data key content will override the vendor-data one.
So e.g. it is impossible to use the `packages:` key in both to install default and instance-specific package.
The bug report exposes that the merging feature of cloud-init is of dubious quality: https://github.com/canonical/cloud-init/issues/6268
This is quite annoying.
PXE autoinstall Ubuntu Desktop 24.04 fails at snapd.seeded.service #cloudinit
Wrote another blog post about my fun trying to get #cloudinit to work on #freebsd running in #hetzner
If anyone has any cool ideas I’m open to suggestions
https://bev.is/posts/2026-04-22-freebsd-on-hetzner-2-cloud-init-boogaloo/
Was messing around with the ansible libvirt collection to deploy some molecule instances. Turns out the virt_install module forgot to add the #cloud-config header to user-data when converting it from dictionary to string. Therefor my cloudinit user never got created. Currently preparing a pull request but I am stuck a bit on the test setup.
Bastien Traverse
AskUbuntu
Grant Bevis
chronicc