[pve-devel] [PATCH container] setup: support Ubuntu 24.04 Noble

[Fiona Ebner]

Am 29.04.24 um 13:11 schrieb Thomas Lamprecht:
> Am 29/04/2024 um 11:56 schrieb Fiona Ebner:
>> Am 29.04.24 um 11:36 schrieb Fiona Ebner:
>>> Am 29.04.24 um 11:23 schrieb Fiona Ebner:
>>>> Reported in the community forum:
>>>> https://forum.proxmox.com/threads/145848/#post-658694
>>>>
>>>> Signed-off-by: Fiona Ebner <f.ebner at proxmox.com>
>>>> ---
>>>>
>>>> Minimally tested, that an upgrade from an existing 23.04 container
>>>> works, there still is network and no obviously bad messages in the
>>>> container's journal.
>>>>
>>> Hmm, while the upgrade did work, starting from an Ubuntu 24.04 template
>>> and setting a static IP does not seem to work, like described here:
>>> https://forum.proxmox.com/threads/145848/post-658058
>>
>> Seems like the ordering of the configuration files is the issue. The
>> following would fix it, but probably needs to be special-cased for new
>> Ubuntu (or new systemd, would still need to check where the change came
>> in exactly) not to mess up existing containers, right?
> 
> Yes, at least that would reduce regression potential of unknown issues.

So this is not new (already present for Ubuntu 23.10) and stems from the
fact that these images from linuxcontainers.org contain:

> root at CT113:~# cat /etc/netplan/10-lxc.yaml 
> network:
>   version: 2
>   ethernets:
>     eth0:
>       dhcp4: true
>       dhcp-identifier: mac

and that generates a configuration that will be ordered before
ours/preferred by systemd-networkd:

> root at CT113:~# networkctl status eth0
> ● 2: eth0                                                                      
>                      Link File: n/a
>                   Network File: /run/systemd/network/10-netplan-eth0.network

Should we still change something in the setup code? I suppose our
template will not have the netplan configuration file and in a way it'd
just be a race to the bottom of being ordered first.