I set up a container over a year ago with a static IP address:
$ lxc network attach lxdbr0 atom eth0 $ lxc config device set atom eth0 ipv4.address 10.248.83.4 [pgoetz@erap-atx pkg]$ ip addr ... 4: lxdbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 2e:29:bb:97:24:52 brd ff:ff:ff:ff:ff:ff inet 10.248.83.1/24 scope global lxdbr0 valid_lft forever preferred_lft forever
This was working at the time I set it up, as I ran updates from the container, but how the static IP address is just gone:
[pgoetz@erap-atx pkg]$ lxc exec atom -- bash root@atom:~# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 7: eth0@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:03:f6:fd brd ff:ff:ff:ff:ff:ff link-netnsid 0
I’m running this on Arch linux, and between the time this was known to work, LXD migrated from the user maintained AUR to the official repo, so there were a couple of automatic updates:
[pgoetz@erap-atx pkg]$ pwd /var/cache/pacman/pkg [pgoetz@erap-atx pkg]$ ls lxd* lxd-3.21-1-x86_64.pkg.tar.zst lxd-4.0.0-1-x86_64.pkg.tar.zst lxd-3.21-2-x86_64.pkg.tar.zst lxd-4.2-1-x86_64.pkg.tar.zst
I’m guessing the automatic upgrade to version 4.x somehow broke the networking? Anyone have any insights on what happened or best way to fix?