LXC Debian 12 brand new, issue with systemd-networkd-wait-online and APT

[sargue]

Hi,

I've created a brand new Debian 12 LXC from the official template on my Proxmox 8 server. I've installed logcheck on the LXC as I usually do. Thanks to that I've noticed that APT "cron" tasks are having some problem with systemd-networkd-wait-online. I've quoted "cron" because I think those tasks are actually triggered using systemd timers.

This is an example of the logs:

de gen. 08 06:19:00 vm-portainer systemd[1]: Starting apt-daily-upgrade.service - Daily apt upgrade and clean activities...
de gen. 08 06:19:30 vm-portainer systemd-networkd-wait-online[153997]: Timeout occurred while waiting for network connectivity.
de gen. 08 06:19:30 vm-portainer apt-helper[153995]: E: Sub-process /lib/systemd/systemd-networkd-wait-online returned an error code (1)
de gen. 08 06:19:31 vm-portainer systemd[1]: apt-daily-upgrade.service: Deactivated successfully.
de gen. 08 06:19:31 vm-portainer systemd[1]: Finished apt-daily-upgrade.service - Daily apt upgrade and clean activities.

As you can see therer's a 30 seconds delay. Doing some search on the forum on systemd-networkd-wait-online I can see this is a source of issues, specially with Debian 12. I've tried to apply some of the tips found there to no avail.

Things I've done so far:

• Install ifupdown2 (to replace ifupdown)
• Listen only on the main interface for the service, changing the ExecStart to /lib/systemd/systemd-networkd-wait-online --interface=eth0

Anyone has any tip about how can I fix this?

 

[Chris]

Hi,
do you require the systemd-networkd service? Otherwise I would suggest to disable it. As you already stated, the container uses ifupdown for network configuration by default.

 

[sargue]

That worked, thank you!

Hi,
do you require the systemd-networkd service? Otherwise I would suggest to disable it. As you already stated, the container uses ifupdown for network configuration by default.