=== TheCaptain8983 is now known as TheCaptain898
[14:36] <yogg> Hi
[14:36] <yogg> I playing around with automated installation of an ubuntu-server (24.04) via a "user-data" file which is stored on the install CD. I have a list of packages which should be installed listed in the "packages:" section.
[14:36] <yogg> In the installer itself every package will be installed by starting a chroot, install one package and close the chroot. This loops over the complete list and takes forever because there is so much overhead. Is there a way to install all the packages in one bulk command?
[14:36] <znf> Does anyone know what scripts does ubuntu run when installing a new kernel version that triggers the changing of the /boot/vmlinuz + initrd.img symlinks? 
[14:37] <znf> I've installed an older kernel than my current running one, and it set up the symlinks (and I'm guessing other defaults) for the older version, which is not something I want 
[14:38] <znf> and the only info I can find online is about how to make grub boot it by editing the configs, which is not something I want to do right now
[14:38] <yogg> znf: i think "/etc/kernel/postinst.d/xx-update-initrd-links"
[14:42] <znf> mkay, that worked
[14:43] <znf> thanks
[15:29] <blackboxsw> yogg: this is related to subiquity and I can see what you are saying w.r.t. one operation per package in list in the ephemeral boot environment due to it's interaction w/ curtin to install in the chroot here https://github.com/canonical/subiquity/blob/main/subiquity/server/controllers/install.py#L689-L725. Not certain offhand if there is a way to batch those pkgs download through the Ubuntu installer(subiquity) packages:
[15:31] <blackboxsw> yogg: but I know the ubuntu installer allows for passing user-data to cloud-init on "first boot" after the installer exits by passing "autoinstall:\n  user-data:\n    packages: [pkg1, pkg2]"  that would allow cloud-init on first boot to batch the installed packages during that first boot (if those packages don't contain required config/services that are required on first boot
[15:33] <blackboxsw> *correction: if those packages don't deliver systemd services that are needed early in first boot of the installed system.
[15:42] <yogg> blackboxsw: thx, I do now a "late-command" and install most of the packages there. Not super pretty works ^^
[15:43] <blackboxsw> yeah, that's an option too. I'd await a subiquity person (I'm cloud-init; like falco-jr) for alternative suggestions if there are some
[15:51] <yogg> One thing that I could not find out yet. Ubuntu "autoinstall" uses nearly the same config as cloud-init as I see and everywhere it is called cloud-init. But it is not cloud-init? Its only similar?
[16:14] <cpete> yogg: Indeed. Autoinstall is just another yaml config, which is often delivered by cloud-config, but they are distint. 
[16:14] <cpete> https://canonical-subiquity.readthedocs-hosted.com/en/latest/explanation/cloudinit-autoinstall-interaction.html
[16:15] <cpete> s/distint/distinct
=== patrick_ is now known as patrick
=== JanC is now known as Guest3954