>The design is based on the idea of a template image. The Ubuntu server
image is ready to boot and on first boot cloud-init handles the tasks
to "instantiate the image".
>Doesn't the autoinstall input generatea cloud-init config that
configures these things?
As i understand it, autoinstall generate both cloud-init config AND template installed on the disk.
When you use cloud-init in main way, you use a default templated OS. Autoinstall replace that part and generate template on the disk, then it could define how the template is.
>The design is based on the idea of a template image. The Ubuntu server
image is ready to boot and on first boot cloud-init handles the tasks
to "instantiate the image".
>Doesn't the autoinstall input generatea cloud-init config that
configures these things?
As i understand it, autoinstall generate both cloud-init config AND template installed on the disk.
When you use cloud-init in main way, you use a default templated OS. Autoinstall replace that part and generate template on the disk, then it could define how the template is.
> mkdir -p /target/ lib/systemd/ system/ cloud-config. service. d \nBefore= getty.target > /target/ lib/systemd/ cloud-config. service. d/10-before- getty.conf
>echo -e "[Unit]
Thanks, lets play with this and add a Before= gdm3.service.