Bug#1009351: systemd: Static IP addressing (from config) in LXC containers not working anymore

[Michael Biebl]

Am 12.04.22 um 12:01 schrieb Claudio Kuenzler:
> 
> On Tue, Apr 12, 2022 at 11:33 AM Michael Biebl <biebl at debian.org 
> <mailto:biebl at debian.org>> wrote:
> 
> 
>     Hm, works fine here, i.e. I can't reproduce your problem.
>     I'm running LXC on a Debian sid host though.
>     Maybe it's something related to your LXC configuration/installation?
> 
> 
> Hi Michael
> 
> LXC host runs on Debian Bullseye.
> 
> ck at host:~$ dpkg -l|egrep "(systemd|lxc)" | awk '{print $2" "$3}'
> dbus-user-session 1.12.20-2
> liblxc1:amd64 1:4.0.6-2
> libnss-systemd:amd64 247.3-6
> libpam-systemd:amd64 247.3-6
> libsystemd0:amd64 247.3-6
> libvirt-daemon-system-systemd 7.0.0-3
> lxc 1:4.0.6-2
> lxcfs 4.0.7-1
> systemd 247.3-6
> systemd-container 247.3-6
> systemd-sysv 247.3-6
> systemd-timesyncd 247.3-6
> I actually see a major difference when comparing a Debian 11.2 vs. a 
> 11.3 container.
> 
> -----------------------------------------------------------
> Inside 11.2 LXC:
> 
> root at 112:~# cat /etc/debian_version
> 11.2
> 
> ck at 112:~$ systemctl list-units|grep network
>    networking.service                  loaded active exited    Raise 
> network interfaces
>    network-online.target               loaded active active    Network 
> is Online
>    network.target                      loaded active active    Network
> 
> 
> Inside 11.3 LXC:
> 
> root at 113test:~# cat /etc/debian_version
> 11.3
> 
> root at 11test:~# systemctl list-units|grep network
>    systemd-networkd.service            loaded active running   Network 
> Service
>    systemd-networkd.socket             loaded active running   Network 
> Service Netlink Socket
>    network.target                      loaded active active    Network
> -----------------------------------------------------------
> 
> Note the different network units.
> Both LXC containers have been setup with the same lxc-download template. 
> Actually a locally modified lxc-download template for our infra so there 
> was definitely no change inside the template.
> Not sure where this change comes from though.

Can you attach the output of
systemctl status systemd-networkd.service
journalctl -ulb systemd-networkd.service

for both containers.

If systemd-networkd wasn't running in your old, 11.2 based container, it 
couldn't interfere with your custom network setup.

This is btw I recommended to disable systemd-networkd as the correct 
solution for your issue.

I'm not actually sure if there is anything to fix here.
You simply have two conflicting networking setups.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20220412/16334776/attachment.sig>