cloud-init in LXD triggers after network is up, so indeed, in your case it won't run.
Your problem is that you have the network defined as DHCP so this will hang your boot and cloud-init. If you had /etc/network/interfaces (or the new cloud-init network-data stuff) marked as "manual", then the network configuration step wouldn't hang and cloud-init would run. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1619238 Title: #cloud-config in user.user-data not running without ip Status in lxc package in Ubuntu: New Bug description: I'm having the darndest issue that a cloud config script that is present in a lxc profile and should beapplied on creation is not being run on boot on any image on three different servers when there is no dhcp server or IP present on spun up image. There is nothing in the logs that indicate an error, the process to apply the cloud data just doesn't run. I can see that data read into /var/lib/cloud/seed/nocloud-net/user-data and it's present. But it is not applied unless I manually give the machine an IP address, not before which is quite annoying as I am applying the IP address through the profile in this instance. The logs are no help, they just say it ran successfully when I add an IP address manually or are silent about running cloud-init when it doesn't have one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1619238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
