=== djhankb2 is now known as djhankb
[15:45] <hybrid512> Hi
[15:46] <hybrid512> I need to run RHEL VMs on LXD but it seems LXD datasource is not working with these VMs
[15:46] <hybrid512> any idea why and how to make it work ?
[15:46] <hybrid512> I'm talking about LXD "VMs" and not "containers"
[16:10] <hybrid512> I tried with RHEL9 ... no more luck :(
[16:11] <minimal> hybrid512: did you look at the cloud-init.log file to see what is happening?
[16:24] <hybrid512> what is happening is that no datasource is detected
[16:24] <hybrid512> /dev/lxd/socket is not created
[16:38] <minimal> the 1st line of the LXD DataSource code states: "Datasource for LXD, reads /dev/lxd/sock representaton of instance data"
[16:38] <minimal> so you mean /dev/lxd/socket or /dev/lxd/sock ?
[16:47] <hybrid512> /dev/lxd/sock, sorry
[16:48] <minimal> that sounds like a LXD-related issue then, not a cloud-init issue
[16:48] <hybrid512> in fact, I made it work with a config disk but not with the LXD native datasource
[16:49] <minimal> ^^^
[16:49] <minimal> as the LXD DataSource relies on the presence of /dev/lxd/sock and /dev/lxd/sock is not actually present then of course the LXD DataSource is not going to work...
[16:50] <hybrid512> well, I don't have time to push for LXD fixes and I need this to work with even older releases (RHEL7) so I'll go for the config disk, this is good for me
[16:50] <hybrid512> thx for your help
[18:01] <blackboxsw> hybrid512: also delayed response, but if /dev/lxd/sock isn't being created, it's possible that the lxc config show <your_vm> shows that `  security.devlxd: "false` If that is set false, the socket isn't exposed to the VM.
[20:41] <hybrid512> @blackboxsw security.devlxd was set to true but still, /dev/lxd/sock doesn't exist inside the RHEL VM (wether it's RHEL 7, 8 or even 9)