build custom windows 10 image vmware iso

lp:maas-images ↗ provides the unmodified SquashFS, installed kernel, and generated initramfs as separate files on. Once everything is installed the kernel and newly generated initramfs are pulled out of the overlay and everything is unmounted.

It then installs a kernel and extra initramfs scripts from the cloud-initramfs-rooturl and cloud-initramfs-copymods packages to allow network booting. The SquashFS does not contain a kernel so lp:maas-images ↗ mounts the SquashFS with an overlay and chroots in. When the MAAS stream ↗ is generated by lp:maas-images ↗ it starts by downloading the base SquashFS rootfs from that is used for all clouds. Why customised Ubuntu deployments aren’t supported

How to create a custom Ubuntu image for MAAS.

Warnings on creating a custom Ubuntu image.

Why customised Ubuntu deployments aren’t supported.

Instead Canonical suggests customising Ubuntu ↗ using cloud-init user_data or Curtin preseed data.

Canonical provides both lp:maas-image-builder ↗ and gh:canonical/packer-maas ↗ to support creating custom images however, these tools do not currently support Ubuntu. MAAS supports deploying custom DD or TGZ images.

Build custom windows 10 image vmware iso