Proxmox testing with community

[tormath1]

A Proxmox image is available here for testing purposes here: http://bincache.flatcar-linux.net/images/amd64/9999.9.100+kai-proxmox-support/flatcar_production_proxmoxve_image.img.bz2.

One can try it following this documentation: https://github.com/flatcar/flatcar-website/pull/337/files or Terraform approach. You can directly suggest your feedback to the documentation or discuss about it in this discussion:

[ader1990]

I could succesfully create and run a Flatcar VM with Ignition on Proxmox VE latest (8.2.2):

export VM_ID=124

qm create $VM_ID --cores 2 --memory 4096 --net0 "virtio,bridge=vmbr0" --ipconfig0 "ip=dhcp"
qm disk import $VM_ID flatcar_production_proxmoxve_image.bin local-lvm

# tell the vm to boot from the imported image
qm set $VM_ID --scsi0 local-lvm:vm-$VM_ID-disk-0
qm set $VM_ID --boot order=scsi0

qm set $VM_ID --ide2 local-lvm:cloudinit

qm set $VM_ID --cicustom "user=local:snippets/userdata"
# userdata is from https://github.com/flatcar/flatcar-website/pull/337/files#diff-47f96e69913e3bf870ccb62bcfad55dda8e04436a2bb2090a1fb7a17f1e57b77R71

qm start $VM_ID

Notes: the hostname is not set in this scenario.
Also, if no cloudinit config drive is configured and attached, the OS will drop into an emergency console.

[tormath1]

Here's a new image: http://bincache.flatcar-linux.net/images/amd64/9999.0.0+103-kai-proxmox-support/flatcar_production_proxmoxve_image.img (without compression as bzipped was not worth it). It also tests this patch: coreos/afterburn#1128.
Could you folks test if everything is still working as expected + if the instance can boot without a config drive? Thanks 🙏

[tormath1]

@ader1990 @donch @fhemberger @mcbenjemaa I gave a try and it boots fine with/without config-drive with the following image ⬆️

[ader1990]

Hello @tormath1, I verified on my local proxmox and it is working as expected: when cloud-init config drive is not attached, Flatcar boots and there is an autologin. Thanks!

[donch]

Hi @tormath1 , I have redone my previous tests and can confirm it still works. Without any cloud-init config drive, the VM starts with autologin enabled. Thank you for your work!

[mcbenjemaa]

great job, I can confirm the image boots fine with/without config-drive.

I wish we could support network-config version 2

[fhemberger]

@mcbenjemaa

Can you try to mount /dev/disk/by-label/cidata into some tmp folder, and let me know what is inside there?

• meta-data: Instance ID
• network-config: DNS-Config (YAML)
• user-data: The ignition.json config provided
• vendor-data: Empty file

[mcbenjemaa]

Please, give me an example of the metadata and network-config

[fhemberger]

core@flatcar ~/test $ cat meta-data
instance-id: ae1808cd94103dab0a5f9dcbc2b93e0b0f8d9b51

core@flatcar ~/test $ cat network-config
version: 1
config:
    - type: nameserver
      address:
      - '192.168.178.1'
      search:
      - 'fritz.box'

[mcbenjemaa]

Thanks

[mcbenjemaa]

I used this userdata:

	userdata := `#cloud-config
hostname: dummy-vm-hostname
manage_etc_hosts: true
fqdn: dummy.local.com
user: dummy-user
password: $5$6LDowW6p$.RyFu8lVH7Cw3AB.pPS/K2lmB8IczVs99A7gbcUCLV2
ssh_authorized_keys:
  - ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDd1hElre4j44sbmULXyO5j6dRnkRFCMjEGtRSy2SuvFD8WyB5uectcEMvz7ORhQIVbPlz94wFjpSX5wl/gmSKL/7GOyerJo0Y2cvyjJJahuDn+JnIL0tT0HS1pJ5iJqQpxXeOAzMK5Heum+uGw9BzbiUHnRzjJr8Ltx4CAGMfubevD4SX32Q8BTQiaU4ZnGtdHo16pWwRsq1f6/UtL4gDCni9vm8QmmGDRloi/pBn1csjKw+volFyu/kSEmGLWow6NuT6TrhGAbMKas5HfYq0Mn3LGPZL7XjqJQ6CO0TzkG/BNplZT2tiwHtsvXsbePTp4ZUi4dkCMz2xR4eikaI1V dummy@dummy.local
chpasswd:
  expire: False
users:
  - default
package_upgrade: true`

But the boot is failing for me.

and i'm pretty confused, if I use an ignition in the userdata, it tells the user-data doesn't have #cloud-config

[fhemberger]

Regular cloud-init config is not supported, only Ignition. Please check the example in the documentation:

https://github.com/enix/flatcar-website/blob/proxmoxve/content/docs/latest/installing/vms/proxmoxve.md#configuring-the-vm-using-ignition

[mcbenjemaa]

i got the issue, it's not about user-data but because of the network-config,
it only accepts an version 1