Comment 17 for bug 1761573

Hi Daniel,

Thanks for commenting. I don't believe your issue is the same as this bug (kernel issue with e1000e driver in the 4.15 kernel). Rather it appears that you're booting a cloud image outside of a cloud and without any cloud configuration.

Cloud-init only runs if it detects that it has been provided configuration from a Datasource. Typically for booting outside of a cloud, the NoCloud datasource[1] is a good option that can help provide minimal configuration.

http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html

Once you've provided a NoCloud datasource to the image, cloud-init will enable itself and run. The default behavior is to DHCP on one of the nics to provide networking.

If you are booting this image in a cloud, please provide the user-data and more details about where you are running the image in a separate bug and we can helps sort out any booting/networking issues you're facing at this time.