I have a server that previously fine containers are misbehaving.
The running container suddenly loses its IP4, then If I stop it with force and do incus network set incusbr0 ipv4.dhcp true and restart it then IP4 will work for a while.
Thankfully, it is only one server.
Any ideas what is going on or how to fix it.
I faced same issue and appear the issue that I have incusbr0 twice in Network Manager, I removed (using nmtui) both of incusbr0 from Network Manager and restart the system then everything back to normal
I am also getting this… only way to shutdown is via Force
root@10TBBACK:~# reboot
System has not been booted with systemd as init system (PID 1). Can’t operate.
Failed to connect to bus: Host is down
Failed to talk to init daemon.
The container images, when they are booted up, they try to receive their network configuration from the network. In both cases I assume that you are using a network that is managed by Incus, the incusbr0.
You would also need to list the container images that you are using, such as images:ubuntu/24.04/cloud.
When you run incus list, you get the IP address of a container as reported either by the container, or by the managed (by Incus) interface. Most likely the latter. Here it’s good to verify in the container what’s going on. In the case of an Ubuntu container with default settings, try
netplan status
With default settings, the above line will say that the container is using networkd for the networking:
● 21: eth0 virtual-ethernet UP (networkd: eth0)
Let’s see what networkd knows about the DHCP allocation. Here is shows you that it got a DHCP lease and from where it got it.
$ networkctl status
...
Jul 17 07:19:08 mycontainer systemd[1]: Started systemd-networkd.service - Network Configuration.
Jul 17 07:19:08 mycontainer systemd[1]: Starting systemd-networkd-wait-online.service - Wait for Network to be Configured...
Jul 17 07:19:08 mycontainer systemd-networkd[211]: eth0: DHCPv4 address 10.10.10.227/24, gateway 10.10.10.1 acquired from 10.10.10.1
Jul 17 07:19:09 mycontainer systemd-networkd[211]: eth0: Gained IPv6LL
Jul 17 07:19:09 mycontainer systemd[1]: Finished systemd-networkd-wait-online.service - Wait for Network to be Configured.
$
In your cases try to debug using the above steps.
Hope this gives you an idea
oot@RR5:/home/rr2020# networkctl status● State: n/a
Online state: unknown
Address: 192.168.1.27 on enp1s0f1
10.119.230.1 on 10.0.0.0
10.126.149.1 on incusbr0
fd42:266e:d72f:8869::1 on 10.0.0.0
fd42:ecf:4f02:b679::1 on incusbr0
fe80::c0f6:cdc:ab5a:e0d1 on enp1s0f1
fe80::1266:6aff:fe80:5f7e on incusbr0
Gateway: 192.168.1.253 on enp1s0f1
fe80::1ac2:41ff:fe2d:9c10 on enp1s0f1
--------------------------incus exec METABASE bash
root@METABASE:~# netplan status
System has not been booted with systemd as init system (PID 1). Can’t operate.
Failed to connect to bus: Host is down
System has not been booted with systemd as init system (PID 1). Can’t operate.
Failed to connect to bus: Host is down
Traceback (most recent call last):
File “/usr/sbin/netplan”, line 23, in
netplan.main()
File “/usr/share/netplan/netplan_cli/cli/core.py”, line 58, in main
self.run_command()
File “/usr/share/netplan/netplan_cli/cli/utils.py”, line 332, in run_command
self.func()
File “/usr/share/netplan/netplan_cli/cli/commands/status.py”, line 77, in run
self.run_command()
File “/usr/share/netplan/netplan_cli/cli/utils.py”, line 332, in run_command
self.func()
File “/usr/share/netplan/netplan_cli/cli/commands/status.py”, line 829, in command
system_state = SystemConfigState(self.ifname, self.all)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/share/netplan/netplan_cli/cli/state.py”, line 437, in init
utils.systemctl(‘start’, [‘systemd-networkd.service’], True)
File “/usr/share/netplan/netplan_cli/cli/utils.py”, line 118, in systemctl
subprocess.check_call(command)
File “/usr/lib/python3.12/subprocess.py”, line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘[‘systemctl’, ‘start’, ‘systemd-networkd.service’]’ returned non-zero exit status 1.
I still do not know what container image is running in those containers. I gave as an example images:ubuntu/24.04/cloud. What is the container image for the affected containers?
When you present the output of commands, please use the Preformatted text environment. It’s the sixth icon in the toolbar above, and looks like </>. You select the pasted text, then hit the button Preformatted text. It makes it easier to figure out the indentation in the text output.
