Public bug reported: The Desktop ISO installer enables cloud-init to allow automation with Subiquity autoinstall. Currently, cloud-init probes & configures networking in the live environment. As described in cloud-init#6110, this does not appear to be necessary as NetworkManager should manage network connectivity in this context.
To be clear, I am proposing this as a workaround for cloud-init#6110. My understanding of the proposed first steps here are to drop the configuration from [2] and instead write netplan configuration in the ISOs directly. One possible pitfall: I did a little bit of additional testing and found that configuring a static IP on the kernel command line in combination with disabled cloud- init network-config generated DNS issues: vmlinuz ip=10.183.135.99::10.183.135.1:255.255.255.0::::10.183.135.1 network-config=disabled The static IP works alright but `resolvectl status` showed no configured DNS servers. A `netplan apply` was sufficient to fix it, as initramfs- tools converts the cmdline into a netplan configuration. [1] https://github.com/canonical/cloud-init/issues/6110 [2] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu/includes.chroot.minimal.standard.live/etc/cloud/cloud.cfg#n23 ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2107225 Title: Disable cloud-init network config in Desktop ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2107225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
