Comment 2 for bug 2050009

I've dived into it further (your link helped a lot here).

Identical set-up:

1. Install Ubuntu Jammy minimal server with HWE kernel
2. Install ubuntu-advantage-tools
3. pro attach
4. pro enable anbox-cloud

From here, the failing server:

$ sudo anbox-cloud-appliance init --auto

At this point the application installs LXD 5.0.

$ snap list
Name Version Rev Tracking Publisher Notes
amc 1.20.2 549 latest/stable canonical✓ -
ams-node-controller 1.20.2 289 - canonical✓ -
anbox-cloud-appliance 1.20.1 506 latest/stable canonical✓ classic
canonical-livepatch 10.7.0 246 latest/stable canonical✓ -
core 16-2.60.4 16202 latest/stable canonical✓ core
core20 20231123 2105 latest/stable canonical✓ base
core22 20231123 1033 latest/stable canonical✓ base
lxd 5.0.2-838e1b2 24322 5.0/stable canonical✓ -
snapd 2.61.1 20671 latest/stable canonical✓ snapd

On the working server:

$ sudo snap install lxd
$ sudo anbox-cloud-appliance init --auto

The default install for LXD seems to be 5.19.

$ snap list
Name Version Rev Tracking Publisher Notes
amc 1.20.2 549 latest/stable canonical✓ -
ams-node-controller 1.20.2 289 - canonical✓ -
anbox-cloud-appliance 1.20.1 506 latest/stable canonical✓ classic
canonical-livepatch 10.7.0 246 latest/stable canonical✓ -
core 16-2.60.4 16202 latest/stable canonical✓ core
core22 20231123 1033 latest/stable canonical✓ base
lxd 5.19-8635f82 26200 latest/stable canonical✓ -
snapd 2.61.1 20671 latest/stable canonical✓ snapd

So something is telling the system to install LXD 5.0, which is causing the init to fail. The reason looks to be the same reason reported in the supplied link.

The init procedure is choosing the wrong version of LXD to install.