I noticed recently on two different laptops running Ubuntu 22 that network connectivity can be lost to containers without a clear way to restore it other than to reinstall Ubuntu 22. Example below.
I tried removing all my containers and then removing lxd, reboot and install again but no result.
In both there is no clear cause. One minute it is working, the next it stops working without any significant thing happening during that time. I am not installing or re-configuring anything. It just suddenly stops working.
What is especially troublesome that there does not seem to be a way to restore network connectivity. Recreating containers doesn’t work. Reinstalling lXD does not work. Reboot does not work.
What could be the cause of this troublesome behavior?
sugarmoose@io3:~$ lxc launch ubuntu:22.04 --vm
Creating the instance
Instance name is: dear-dassie
Starting dear-dassie
sugarmoose@io3:~$ lxc exec dear-dassie bash
root@dear-dassie:~# wget google.nl
--2023-03-21 07:43:51-- http://google.nl/
Resolving google.nl (google.nl)... 142.251.39.99, 2a00:1450:400e:811::2003
Connecting to google.nl (google.nl)|142.251.39.99|:80...
root@dear-dassie:~# ip a
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
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:16:3e:5c:09:74 brd ff:ff:ff:ff:ff:ff
inet 10.94.57.182/24 metric 100 brd 10.94.57.255 scope global dynamic enp5s0
valid_lft 3209sec preferred_lft 3209sec
inet6 fe80::216:3eff:fe5c:974/64 scope link
valid_lft forever preferred_lft forever
3: enp6s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:16:3e:cc:27:b8 brd ff:ff:ff:ff:ff:ff
root@dear-dassie:~#