/srv/irclogs.ubuntu.com/2022/06/28/#cloud-init.txt

=== djhankb2 is now known as djhankb
hybrid512Hi15:45
hybrid512I need to run RHEL VMs on LXD but it seems LXD datasource is not working with these VMs15:46
hybrid512any idea why and how to make it work ?15:46
hybrid512I'm talking about LXD "VMs" and not "containers"15:46
hybrid512I tried with RHEL9 ... no more luck :(16:10
minimalhybrid512: did you look at the cloud-init.log file to see what is happening?16:11
hybrid512what is happening is that no datasource is detected16:24
hybrid512/dev/lxd/socket is not created16:24
minimalthe 1st line of the LXD DataSource code states: "Datasource for LXD, reads /dev/lxd/sock representaton of instance data"16:38
minimalso you mean /dev/lxd/socket or /dev/lxd/sock ?16:38
hybrid512/dev/lxd/sock, sorry16:47
minimalthat sounds like a LXD-related issue then, not a cloud-init issue16:48
hybrid512in fact, I made it work with a config disk but not with the LXD native datasource16:48
minimal^^^16:49
minimalas 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:49
hybrid512well, 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 me16:50
hybrid512thx for your help16:50
blackboxswhybrid512: 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.18:01
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)20:41

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!