On Tue, 16 Jun 2020 at 11:10, Ryan Harper <email address hidden>
wrote:
> Hrm, the cloud-init.tar.gz seems to have an empty /run ... I really
> wanted to see the /run/cloud-init/.ds-identify.result,ds-
> identify.log,cloud.cfg
>
Well I had to dig it out of a disk image because I couldn't log in to the
VM in this case... There are ways to make this possible I guess but a bit
tedious.
In any case, it's fairly clear what happens here when you read the source
for DataSourceNoCloud: filesystems with the relevant label are checked
after self.seed_dirs, and so any user-data there wins.
On Tue, 16 Jun 2020 at 11:10, Ryan Harper <email address hidden>
wrote:
> Hrm, the cloud-init.tar.gz seems to have an empty /run ... I really init/.ds- identify. result, ds- log,cloud. cfg
> wanted to see the /run/cloud-
> identify.
>
Well I had to dig it out of a disk image because I couldn't log in to the
VM in this case... There are ways to make this possible I guess but a bit
tedious.
In any case, it's fairly clear what happens here when you read the source
for DataSourceNoCloud: filesystems with the relevant label are checked
after self.seed_dirs, and so any user-data there wins.