test(24.04): add LXD backend to Spread

[cjdcordeiro]

(same as #316 , for 24.04)

[github-actions]

Diff of dependencies:
None found.

---

[cjdcordeiro]

@Meulengracht can you please check if this fixes your privileged tests? (use spread lxd)

[Meulengracht]

@Meulengracht can you please check if this fixes your privileged tests? (use spread lxd)

lxd fails to come up, it's stuck doing lxc exec ubuntu-noble -- pgrep sshd

[cjdcordeiro]

@Meulengracht but can you even launch an lxd instance outside spread? If you do lxd launch ubuntu:24.04 u1, will it come up?

[Meulengracht]

@Meulengracht but can you even launch an lxd instance outside spread? If you do lxd launch ubuntu:24.04 u1, will it come up?

Yea it works just fine - I use lxd for multiple purposes

[cjdcordeiro]

And when you say it's stuck, does it timeout? Note that LXD will first pull/refresh the image, which could take a while depending on your connection.

If you do the lxc launch... I mentioned above and then spread lxd, will it still get stuck?

[linostar]

And when you say it's stuck, does it timeout? Note that LXD will first pull/refresh the image, which could take a while depending on your connection.

If you do the lxc launch... I mentioned above and then spread lxd, will it still get stuck?

Isn't that because this PR needs #317?

[linostar]

LGTM, thanks!

[Meulengracht]

And when you say it's stuck, does it timeout? Note that LXD will first pull/refresh the image, which could take a while depending on your connection.

If you do the lxc launch... I mentioned above and then spread lxd, will it still get stuck?

Sorry for the incredibly slow reply here - So I looked a bit more into this, it seems that sshd does not come up, it tells me the service unit does not exist. The container is running fine, and I can shell into it.

root@ubuntu-noble:~# systemctl status sshd
Unit sshd.service could not be found.

[Meulengracht]

Added a suggestion for improvement. That fixed it for me

[rebornplusplus]

Looks good to me! Hope it works! 🤞