Bug#1055786: GID=1000 for netdev created by cloud-init violates Debian Policy

[Osamu Aoki <osamu@debian.org>]

HI,

On Fri, 2023-12-08 at 21:36 -0800, Ross Vandegrift wrote:

On Mon, Nov 13, 2023 at 01:48:09PM +0900, Osamu Aoki wrote:

But not for LXD since it uses different images.  Image normally downloaded and

used by `lxc launch ...` becomes buggy once its instance is started because then

cloud-init starts system initialization with its default setting.

Oh right, that's what I wasn't putting together.  Sorry for making you repeat

yourself.

Here is how I get around this problem by removing toxic netdev out of installed

file /etc/cloud/cloud.cfg:

Is unusual GID numbering the only impact, or does this cause more significant

problems?  I guess user code that tries to statically assign GID 1000 will

break.

Yes.  Although UID=1000, GID=1000 is expected it is not guaranteed.

I agree it should be fixed.  In unstable it seems reasonable to change the

config.  But I'm not sure I think it warrants a stable update.

For stable, if you have chance to update, please consider to add README or just keep this bug open for bookworm.

README should have workaround as I wrote:

    https://osamuaoki.github.io/en/2023/11/12/lxc-2/#configuration-of-lxd-instance

(While wait and bug upstream LXD image generation code to fix it to address this issue.

   https://github.com/canonical/cloud-init/issues/4603#issuecomment-1827955514

For unstable, please consider to limit groups listed to ones in base-config.

Regards,

Osamu