I built a new UC16 image with the systemd proposed package. Initially networkd running early is fine. However, under closer inspection, in a networkd-only image, DNS (resolvconf) was not running early enough to allow DNS service to be available at the time that cloud-init.service runs (which may look up resources via hostnames).
After some discussion, the following change is also needed in resolvconf to ensure that in a networkd-based image, that we get DNS early along with networkd early.
I built a new UC16 image with the systemd proposed package. Initially networkd running early is fine. However, under closer inspection, in a networkd-only image, DNS (resolvconf) was not running early enough to allow DNS service to be available at the time that cloud-init.service runs (which may look up resources via hostnames).
After some discussion, the following change is also needed in resolvconf to ensure that in a networkd-based image, that we get DNS early along with networkd early.
% diff -u resolvconf. service. orig resolvconf.service service. orig 2016-12-06 04:58:43.202698062 -0600 man:resolvconf( 8) ncies=no networking. service systemd- networkd. service
--- resolvconf.
+++ resolvconf.service 2016-12-06 04:58:50.367042811 -0600
@@ -3,6 +3,7 @@
Documentation=
DefaultDepende
Before=
+Before=
[Service] t=yes
RemainAfterExi