resolv.conf magically disappears on boot, causing network to not work
seems to happen consistently upon first boot, when casper-rw is empty
Well, it's not present at all in the squashfs image. Normally it is created by the DHCP client when you restart the network. But that seems to be broken for you.
Bug watches keep track of this bug in other bug trackers.
seems to happen consistently upon first boot, when casper-rw is empty