Comment 6 for bug 1819871

Latest version in the FreeBSD ports: 18.3 ( with local patchest: https://svnweb.freebsd.org/ports/head/net/cloud-init/files/ ) << btw, maybe there is a chance to add it to upstream?

Im also try latest cloud-init release from https://launchpad.net/cloud-init (18.5) but no luck.

I talked to some people who use cloud-init on FreeBSD on Azure and OpenStack cloud. No one seems to have problems, because in these clouds information is received through HTTP and all fine. I seem to be the first person on the planet who tried cloud-init with local storages.

as for the rest of the questions:

I do not use ready-made FreeBSD cloud instance ( despite the fact that the project also makes them: http://ftp.freebsd.org/pub/FreeBSD/releases/VM-IMAGES/12.0-RELEASE/amd64/Latest/ ). I need to create my own image, so i can write how to reproduce environment from the scratch:

1) download latest official FreeBSD release:

wget https://download.freebsd.org/ftp/releases/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-RELEASE-amd64-disc1.iso

2) run it in any hypervisor ( personally i run in bhyve but it doesn't matter ) and install as usual

3) restart guest domain after install with proper seed.iso

4) inside guest: change pkg repository from quarterly to latest:

    sed -i'' 's:quarterly:latest:g' /etc/pkg/FreeBSD.conf

5) install cloud-init:

     pkg update -f
     pkg install -y net/cloud-init

6) try to run cloudinit[local]

despite the fact that 'cidata' exist on media via ( glabel status -s ), cloud-init doesn't use it.

ps: unfortunately i'm not familiar with the cloud-init code. But if anything - I am ready to help solve the problem ( testing, consultations on FreeBSD commands so on )