cloud-init "nocloud" networking setup

README.md

cloud-init is absolute cancer. Its code is horrible. It has no documentation at all.

It took me 5 fucking hours to figure out how to properly configure networking on recent cloud-init (Ubuntu 16.04 cloud image) with local datasource.

It's not mentioned anywhere you need to provide dsmode: local. (but only if you need network-config, besides that everything is fine; someone below noted that -m flag does the same thing, good to know) Of course nobody needs documentation for network-config format either. (cloudinit/net/__init__.py is a protip, enjoy the feces dive)

Oh, and by the way - no, it's not possible to provide network-config to uvt-kvm without patching shit.

Use -N flag for cloud-localds for network-config.

meta-data

dsmode: local
# ↑ THIS. SHIT.

network-config

---
version: 1
config:
 - type: physical
   name: ens3
   subnets:
    - control: auto
      type: static
      address: |
         192.168.21.37
             pre-up echo xD > /tmp/yesitsthereyo # quality configuration injection, real thing

user-data

#cloud-config
chpasswd:
  list: |
    root:password
  expire: False
write_files:
  - content: |
    You don't really need that, just a bloody test.
  path: /root/test.txt

Hi guys,
I just started to get to know cloud-init but facing some misunderstanding already, so maybe you can help me with.

Troubleshooting Steps Taken:
Instance Metadata Service:

• Confirmed that the instance metadata service is configured properly (at least from what I can see).
  Cloud-Init Configuration:

• Running cloud-init --version shows version 23.x.

• Reviewed cloud-init configuration files in /etc/cloud/cloud.cfg and /etc/cloud/cloud.cfg.d/, and everything seems fine on the surface.
  Packer Version Compatibility:

• Running packer version shows version 1.7.1. to build AlmaLinux 9 GenericCloud image with cloud-init. When device boot it did not start cloud-init as service keep disabled. Once I run "cloud-init init" then I got error as you can see on the attached screenshot.
  Haven’t found any clear compatibility issues in the Packer documentation.
  Logs:

• Checked /var/log/cloud-init.log and /var/log/cloud-init-output.log, and the main issue seems to be the timeout when trying to reach the metadata URLs.
  Questions:

• Has anyone encountered a similar issue where cloud-init times out trying to reach the metadata service? Even tho that I placed my meta data under /var/lib/cloud/seed/nocloud

• Are there specific versions of cloud-init or Packer that are known to be problematic in this context?

• Could this be related to some VPC or instance configuration that I might be overlooking?

• Any suggestions on further troubleshooting steps I should take?
  I appreciate any insights or suggestions you can provide.
  Thank you!

cloud-init is absolute cancer. Its code is horrible. 🤣🤣
It has no documentation at all

This saved me so much time! Fuck it, why even bother having one config for different network managers? Just a few run commands on the network manager and it was done. Mostly different cloud-config files for each linux distro anyway.