Open parmentelat opened 1 year ago
as a side note to self, after boot with the u18 image only minimally modified, I can see this
systemctl start cloud-init
manually, the .ssh/
folder gets created and populated as expectedas a second note, I got an insight on the cloud-init irc libera channel, where I learned that:
providing the extended kernel params after --- cloud-init=enabled will enable cloud-init in BIonic's ephemeral boot stage
so this answers my questions 1 and 2. I guess :) I'm still interested to hear your thoughts about question3, particularly wrt https://discourse.ubuntu.com/t/cloud-init-and-the-live-server-installer/14597 where you announced a change in the u20 installer chain...
18.04 is deprecated in a few weeks, right?
hiya
I'm trying to create custom bootcd's from ubuntus 18 20 and 22 that I could use as live-only boot supports I've been kind of successful with 20 and 22 so far, using a hand-made shell script of my own brew - before I stumbled onto this repo which I will probably leverage as it's much cleaner than my own stuff :)
regardless, my approach was working fine with 20 and 22, but fails to work with 18 and I am suspecting the presence of
/etc/cloud/cloud-init.disabled
to be the root problemto be more specific:
cidata
and that is enough for cloud-init to spot it; I can tell thatcloud-init
performs because my custom ssh keys get installed.ssh/
created, there is no file named as/var/log/*cloud*
, nor doesjournalctl -u cloud-init.service
report anything at allso I guess I have 3 questions
livefs-editor
to remove that file in/etc/
?livefs-editor
?thanks !