[18:39] <Steve37> Hey all, hoping I could get some help with an annoying configuration problem. Here's my setup: I have a VM booting an Ubuntu image with no NICs attached. I am not allowed to modify the image itself. What I am allowed to do is have full control over the user-data passed to it. This user-data is passed via a NoCloud disk image, so I have access to
[18:39] <Steve37> cloud-init-local. The problem I'm having is that by default this Ubuntu image runs systemd-networkd-wait-online, which takes 2 minutes to time out before boot can continue. This is a problem, and I'd very much like to make it go away. Since the VM has no NICs, it will never have an internet connection, but I can't find a way to make systemd see
[18:39] <Steve37> this. I've tried passing `network: config: disabled` in my user-data, but nothing seemed to change. Does anyone have any ideas on what exactly I can specify that'll make cloud-init-local get rid of this for me?
[18:42] <Steve37> I should clarify: the image has the full cloud-init service depending on systemd-networkd-wait-online, so I can't use something like bootcmd or runcmd to just mask it.
[20:39] <falcojr> Steve37: you could try adding a network-config to your NoCloud image. You can see an example here (under the example): https://cloudinit.readthedocs.io/en/latest/reference/datasources/nocloud.html#example-meta-data 
[20:40] <falcojr> if you list a single interface with "optional: true", I'm wondering if that would work