Fedora based LXC containers and no network on startup

[fazowy]

Hi.

After pve-container package upgrade from 4.4-4 to 4.4-6 LXC containers based on Fedora image do not start with systemd-networkd service enabled. Little spelunking into proxmox git repository gives this commit:

add setup_systemd_preset helper, disable networkd for debian 12+
https://git.proxmox.com/?p=pve-container.git;a=commit;h=e11806e0de064e6570d40e7c04bc4656687b2c62

and diff for Fedora.pm

--- a/src/PVE/LXC/Setup/Fedora.pm
+++ b/src/PVE/LXC/Setup/Fedora.pm
@@ -35,13 +35,12 @@ sub setup_init {
     my $version = $self->{version};
 
     if ($version >= 37) {
-       # systemd-networkd is disabled by the preset in >=37, reenable it
        # this only affects the first-boot (if no /etc/machien-id exists).
-       $self->ct_mkdir('/etc/systemd/system-preset', 0755);
-       $self->ct_file_set_contents(
-           '/etc/systemd/system-preset/00-pve.preset',
-           "enable systemd-networkd.service\n",
-       );
+       $self->setup_systemd_preset({
+           # systemd-networkd is disabled by the preset in >=37 in favor of
+           # NetworkManager, reenable it, since we make use of it.
+           'systemd-networkd.service' => 0,
+       });
     }
 }

Looks like description is ok but there is a typo in implementation:
'systemd-networkd.service' is set to 0, should be 1.

 

[Stoiko Ivanov]

Thanks for the report!
I could reproduce the issue and sent a patch to the pve-devel list:
https://lists.proxmox.com/pipermail/pve-devel/2023-June/057898.html

Once it or an improved version has been applied and packaged the issue should be gone!

 

[Baas]

Lovely, thanks, was banging my head to "is my network config for the node broken"! :-D

 

[alpha754293]

It looks like that this is still broken in late April 2024.

(Just downloaded the Fedora 38 LXC template, and it still reports that the network is down on first start up.)