Comment 1 for bug 1810859

Hi, I have similar concern here.

We want to use cloud-init with NoCloud DataSource, as we run our instances on vmWare vSphere which have no metadata server.

So we put our meta-data and user-data files in /var/lib/cloud/seed/nocloud/ directory. But our /var is on a logical volume which is not mounted when cloudinit generator run ds-identify script. ds-identify then exit 1 and cloudinit is not enabled.

Would it be possible to have an option as Robert S. suggested or would it be possible to change Nocloud seed directory to another directory which is not likely to be on a separated filesystem ?

Regards,
Guillaume C.

Ran cloud-init version 18.2-27-g6ef92c98-0ubuntu1~18.04.1