I’ve been running my head into this for days and I’m out of ideas of what to try. Rather than dump what may or may not be useful into the initial post, I’m going to sketch out the problem and hopefully be pointed in the right direction for troubleshooting this and then we can get specific.
The long & short of it is this: I have a CentOS 7.6 image I’m attempting to deploy on a CentOS 7.6 host via LXD 3.16. I’m using the two-tarball method of rootfs and metadata importing into LXC. The rootfs is a chroot install of a corporate CentOS 7.6 image, not one from the LXD images repo. I did not use
distrobuilder to create what was imported as I have just discovered it and tar’ing these up myself and importing was working fine.
I’m attempting to use
cloud-init to set the network configs of the container interface since I don’t have a DHCP server available on this network. The
cloud-init (18.2) RPM was installed into the image source file system.
When I don’t mention the cloud-init templates in
metadata.yaml, the container launches fine.
When I add the template stanzas in, the container refuses to launch or subsequently start. The log error is “No such file or directory” — but which?
The formatting of the templates section matches that of the examples. Each of the files I reference is in the templates directory, which is included in the metadata tarball and I’ve confirmed on the target host that it still is via an
lxc export. What could it possibly be looking for that is not there? Which direction do I move in?