Closed tomastzn closed 2 years ago
Hi. I will modify the help text for this option as is only intended for physical machines (where it is used to create the user-data.yaml contents in the cidata partition).
For non-physical machines SSH public keys that are permitted for accessing any users are set via user-data sections global "ssh_authorized_keys:" setting (only applies for default user "alpine") or the "ssh_authorized_keys:" value inside the "users:" section.
I will add some logic to give an error if this option is specified for a non-physical machine.
Created script with following options:
Converted the image to
vmdk
type with following command:Booted up a VM on ESXI host with the generated disk image and could not log in over SSH. Logging in locally with provided user name and password worked and the public key provided on the command line was no where to be found.
It seems the the option is either being ignored, or the default cloud-init is overwriting it at boot time, or it has to be provided by different means.