Comment 1 for bug 1633656

Looks to me like the network: config: disabled bit should just go in the original cloud-config file, so that is a bit of a red herring.

But DHCP is still happening. It might be being done by networking.service - it seems that cloud-init mostly runs after networking has started up.

There is a cloud-init local step before networking has come up, but it doesn't seem to run bootcmd then?