As suggested on IRC, I'm wondering if we couldn't fix the race by doing the following changes:
- change network-interface to: "start on net-device-added and mounted MOUNTPOINT=/run"
- change resolvconf to: "start on mounted MOUNTPOINT=/run or starting network-interface"
networking.conf should be fine as it's "local-filesystems and (stopped udevtrigger or container))" which should be triggered quite a bit after virtual-filesystems, so resolvconf should have run already.
As suggested on IRC, I'm wondering if we couldn't fix the race by doing the following changes:
- change network-interface to: "start on net-device-added and mounted MOUNTPOINT=/run"
- change resolvconf to: "start on mounted MOUNTPOINT=/run or starting network-interface"
networking.conf should be fine as it's "local-filesystems and (stopped udevtrigger or container))" which should be triggered quite a bit after virtual- filesystems, so resolvconf should have run already.