You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 problem
to be more specific:
with 20 and 22 I expose another ISO volume named cidata and that is enough for cloud-init to spot it; I can tell that cloud-init performs because my custom ssh keys get installed
with 18, there's no .ssh/ created, there is no file named as /var/log/*cloud*, nor does journalctl -u cloud-init.service report anything at all
so I guess I have 3 questions
am I right to suspect the presence of this file to be the root cause of my problem ?
can I use livefs-editor to remove that file in /etc/ ?
more generally, I've taken good note of your disclaimer in the readme :), but in your experience, is it safe to consider editing an image as old as u18.04 with livefs-editor ?
thanks !
The text was updated successfully, but these errors were encountered:
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 !
The text was updated successfully, but these errors were encountered: