Variants, cloud vs default

LXD
1

I’ve noticed that for the images provided by images.linuxcontainers.org there seems to be a ‘default’ and a ‘cloud’ variant of pretty much every image. What is the difference between these? I’ve done a bunch of searching but haven’t found anything about this.

1 Like
2

Cloud images will support cloud-init

The standard ones wont

There may be more differences i am unaware off

3

Nope, that’s pretty much it. That variant includes cloud-init and the required template files to have cloud-init run on startup.

4

Okay great. Is this mentioned anywhere? When you start googling around for “lxd cloud-init” most of the pages that some up explicitly mention that the images provided by images.linuxcontainers.org don’t support cloud-init out of the box. Seems like that has changed.

5

Its a relativly new change

6

I write a quick post about this at

4 Likes
7

Hello,
Please note this thread is the top google link for
“linuxcontainers what is cloud versus default ?”

Even though that is an essential question to answer when picking an LXC file

Such as in my current case

https://images.linuxcontainers.org/images/debian/trixie/amd64/

I could not find a clear answer in the documentation regarding the difference between the two images.

Can it be confirmed that installation and operation of cloud-init is the only difference between these two lxc container version ?

Thanks !

EDIT:
I ask because I need to know if there are any networking configuration changes between the two versions
while I hunt bugs related to making the debian 13 lxc work on proxmox which yields the following errors, and I’d like to exclude the default/cloud choice as the cause

unable to open file '/etc/network/interfaces.tmp.341020' - No such file or directory
unable to create CT 1800 - error in setup task PVE::LXC::Setup::post_create_hook
missing 'arch' - internal error at /usr/share/perl5/PVE/LXC.pm line 661.
8

You can confirm this by looking at the distrobuilder configs here.

Certain steps are labelled variants: // -cloud which are only applied to the cloud variant. (And in the case of debian, some steps are workarounds specific to bullseye cloud)