Closed till closed 5 months ago
Found an example in one of your other repositories ๐๐ผ : https://github.com/virt-lightning/cloud-init-bsd-testing/blob/master/user_data
I think my key was not in "expected" format:
users:
- default
- name: till
sudo: ALL=(ALL) NOPASSWD:ALL
ssh_authorized_keys:
- - ssh-rsa hash==
+ - ssh-rsa hash== till@local
And from there, I also answered my first question: I found it by including default
in the list of users (which I guess is another cloud-init oddity) that it would create a freebsd
user and showed a comment/description from OpenStack.
Most openstack images create a user when a key is injected, so for example ubuntu
or centos
. Not entirely sure what Debian does, I haven't booted that in a long time.
Would you be open to changing that? I can probably work up a PR if you let me know where.
Most openstack images create a user when a key is injected, so for example
ubuntu
orcentos
. Not entirely sure what Debian does, I haven't booted that in a long time.Would you be open to changing that? I can probably work up a PR if you let me know where.
Just found /etc/cloud/cloud.cfg
and it already does this, but I ruined it by trying cloud-config first. :)
Could we add this to the readme? Maybe without the Ansible.
- name: Export the images
command: 'qemu-img convert -f raw -O qcow2 -c images/basehost/builder/final.raw /var/lib/virt-lightning/pool/upstream/{{ final_name }}_exp.qcow2'
args:
creates: '/var/lib/virt-lightning/pool/upstream/{{ final_name }}_exp.qcow2
Sorry for being slow on this. This is a good idea. Could you open up a PR for that?
You mean the bit about building an image?
Never mind, I misunderstood your previous comment. We don't really need to mention this step since the images are already compressed (the -c
).
Hey ๐๐ผ !
Thanks for publishing these images, I am trying to use the 13.0 one and got excited when I saw that you had cloud-init included. :D
Few questions, from scrolling through the repo.
Here is the
cloud-config
I used:It sorta work, but I can't login (it'll ask me for password). I scrolled through the log, I noticed it discovered my dhcp settings and created an account (even though I can't login).