long story short - I’ve 3 other distros based containers running on this ubuntu 24.04 host (a kvm based vm) and they works well so far. But the Rocky 9 refuses to start.
# root @ u24-incus-utils in ~ [23:05:07]
$ incus list -c nsum4Nd
+---------------+---------+-----------+--------------+------------------------+-----------+-------------+
| NAME | STATE | CPU USAGE | MEMORY USAGE | IPV4 | PROCESSES | DESCRIPTION |
+---------------+---------+-----------+--------------+------------------------+-----------+-------------+
| d11-http-file | RUNNING | 0s | 74.05MiB | 192.168.103.220 (eth0) | 15 | |
+---------------+---------+-----------+--------------+------------------------+-----------+-------------+
| d11-wine | RUNNING | 1s | 59.81MiB | 192.168.103.28 (eth0) | 11 | |
+---------------+---------+-----------+--------------+------------------------+-----------+-------------+
| rk9-zab7-pxy | STOPPED | | | | | |
+---------------+---------+-----------+--------------+------------------------+-----------+-------------+
| ub24-ocr | RUNNING | 3s | 113.71MiB | 192.168.103.127 (eth0) | 19 | |
+---------------+---------+-----------+--------------+------------------------+-----------+-------------+
Tried to find out something from system journal, but it’s kinda beyond my capability. I got what happened but don’t know why. And a brand new container from clean image brought no luck neither.
# root @ u24-incus-utils in ~ [22:35:51] C:130
$ incus config show rk9-zab7-pxy
architecture: x86_64
config:
image.architecture: amd64
image.description: Rockylinux 9 amd64 (20240417_02:06)
image.os: Rockylinux
image.release: "9"
image.requirements.cdrom_agent: "true"
image.serial: "20240417_02:06"
image.type: squashfs
image.variant: cloud
raw.lxc: lxc.apparmor.profile=unconfined
volatile.base_image: 4c66eede6e0d5b09b7200b2ac70138be217906e4e4be34b4bd7a5e9f801789a5
volatile.cloud-init.instance-id: 16e2a345-fbf6-4966-ba76-31922c65b9b8
volatile.eth0.hwaddr: 00:16:3e:bd:0f:83
volatile.idmap.base: "0"
volatile.idmap.current: '[{"Isuid":true,"Isgid":false,"Hostid":1000000,"Nsid":0,"Maprange":1000000000},{"Isuid":false,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
volatile.idmap.next: '[{"Isuid":true,"Isgid":false,"Hostid":1000000,"Nsid":0,"Maprange":1000000000},{"Isuid":false,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
volatile.last_state.idmap: '[]'
volatile.last_state.power: STOPPED
volatile.last_state.ready: "false"
volatile.uuid: fdc25cdf-cd18-4b9d-b69c-d3f9d2315fe1
volatile.uuid.generation: fdc25cdf-cd18-4b9d-b69c-d3f9d2315fe1
devices: {}
ephemeral: false
profiles:
- default
stateful: false
description: ""
# root @ u24-incus-utils in ~ [22:36:01]
$ journalctl -f -n 46
Oct 30 22:31:29 u24-incus-utils systemd-networkd[719]: veth5428979b: Link UP
Oct 30 22:31:29 u24-incus-utils kernel: br-incus0: port 4(veth5428979b) entered blocking state
Oct 30 22:31:29 u24-incus-utils kernel: br-incus0: port 4(veth5428979b) entered disabled state
Oct 30 22:31:29 u24-incus-utils networkd-dispatcher[777]: WARNING:Unknown index 13 seen, reloading interface list
Oct 30 22:31:29 u24-incus-utils kernel: veth5428979b: entered allmulticast mode
Oct 30 22:31:29 u24-incus-utils kernel: veth5428979b: entered promiscuous mode
Oct 30 22:31:30 u24-incus-utils systemd[1]: networkd-dispatcher.service: Got notification message from PID 2474, but reception only permitted for main PID 777
Oct 30 22:31:30 u24-incus-utils systemd[1]: networkd-dispatcher.service: Got notification message from PID 2483, but reception only permitted for main PID 777
Oct 30 22:31:30 u24-incus-utils kernel: audit: type=1400 audit(1761834690.083:147): apparmor="STATUS" operation="profile_load" profile="unconfined" name="incus-rk9-zab7-pxy_</var/lib/incus>" pid=2502 comm="apparmor_parse
r"
Oct 30 22:31:30 u24-incus-utils kernel: phys4HFvnk: renamed from veth1fa6bbba
Oct 30 22:31:30 u24-incus-utils kernel: eth0: renamed from phys4HFvnk
Oct 30 22:31:30 u24-incus-utils kernel: br-incus0: port 4(veth5428979b) entered blocking state
Oct 30 22:31:30 u24-incus-utils kernel: br-incus0: port 4(veth5428979b) entered forwarding state
Oct 30 22:31:30 u24-incus-utils kernel: audit: type=1400 audit(1761834690.124:148): apparmor="ALLOWED" operation="open" class="file" profile="/usr/sbin/sssd" name="/sys/devices/virtual/net/veth5428979b/type" pid=786 comm
="sssd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Oct 30 22:31:30 u24-incus-utils kernel: audit: type=1400 audit(1761834690.124:149): apparmor="ALLOWED" operation="open" class="file" profile="/usr/sbin/sssd" name="/sys/devices/virtual/net/veth5428979b/type" pid=786 comm
="sssd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Oct 30 22:31:30 u24-incus-utils kernel: audit: type=1400 audit(1761834690.124:150): apparmor="ALLOWED" operation="open" class="file" profile="/usr/sbin/sssd" name="/sys/devices/virtual/net/veth5428979b/type" pid=786 comm
="sssd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Oct 30 22:31:30 u24-incus-utils systemd-networkd[719]: veth5428979b: Gained carrier
Oct 30 22:31:30 u24-incus-utils kernel: br-incus0: port 4(veth5428979b) entered disabled state
Oct 30 22:31:30 u24-incus-utils kernel: veth1fa6bbba: renamed from phys4HFvnk
Oct 30 22:31:30 u24-incus-utils networkd-dispatcher[777]: WARNING:Unknown index 13 seen, reloading interface list
Oct 30 22:31:30 u24-incus-utils systemd-networkd[719]: veth5428979b: Lost carrier
Oct 30 22:31:30 u24-incus-utils systemd-networkd[719]: phys4HFvnk: Interface name change detected, renamed to veth1fa6bbba.
Oct 30 22:31:30 u24-incus-utils systemd[1]: networkd-dispatcher.service: Got notification message from PID 2527, but reception only permitted for main PID 777
Oct 30 22:31:30 u24-incus-utils systemd[1]: networkd-dispatcher.service: Got notification message from PID 2535, but reception only permitted for main PID 777
Oct 30 22:31:30 u24-incus-utils kernel: veth5428979b: left allmulticast mode
Oct 30 22:31:30 u24-incus-utils kernel: veth5428979b: left promiscuous mode
Oct 30 22:31:30 u24-incus-utils kernel: br-incus0: port 4(veth5428979b) entered disabled state
Oct 30 22:31:30 u24-incus-utils systemd-networkd[719]: veth5428979b: Link UP
Oct 30 22:31:30 u24-incus-utils networkd-dispatcher[777]: WARNING:Unknown index 14 seen, reloading interface list
Oct 30 22:31:30 u24-incus-utils systemd-networkd[719]: veth5428979b: Link DOWN
Oct 30 22:31:30 u24-incus-utils systemd[1]: networkd-dispatcher.service: Got notification message from PID 2545, but reception only permitted for main PID 777
Oct 30 22:31:30 u24-incus-utils networkd-dispatcher[777]: ERROR:Unknown interface index 14 seen even after reload
Oct 30 22:31:30 u24-incus-utils networkd-dispatcher[777]: WARNING:Unknown index 14 seen, reloading interface list
Oct 30 22:31:30 u24-incus-utils systemd[1]: networkd-dispatcher.service: Got notification message from PID 2550, but reception only permitted for main PID 777
Oct 30 22:31:30 u24-incus-utils networkd-dispatcher[777]: ERROR:Unknown interface index 14 seen even after reload
Oct 30 22:31:30 u24-incus-utils networkd-dispatcher[777]: WARNING:Unknown index 14 seen, reloading interface list
Oct 30 22:31:30 u24-incus-utils incusd[894]: time="2025-10-30T22:31:30+08:00" level=warning msg="Failed to set OOM priority" err="Failed to set OOM priority: instance not running or PID not found" instance=rk9-zab7-pxy i
nstanceType=container project=default
Oct 30 22:31:30 u24-incus-utils systemd[1]: networkd-dispatcher.service: Got notification message from PID 2551, but reception only permitted for main PID 777
Oct 30 22:31:30 u24-incus-utils networkd-dispatcher[777]: ERROR:Unknown interface index 14 seen even after reload
Oct 30 22:31:30 u24-incus-utils kernel: audit: type=1400 audit(1761834690.836:151): apparmor="STATUS" operation="profile_remove" profile="unconfined" name="incus-rk9-zab7-pxy_</var/lib/incus>" pid=2567 comm="apparmor_parser"
Then I think I should try the similar stuff on another incus host, which is Debian 12 based kvm vm. It turns out that Rocky Linux 9 lxc runs quite well on that.
Oct 30 22:55:35 aqui-vm-lxd systemd-networkd[483]: veth103185f9: Link UP
Oct 30 22:55:35 aqui-vm-lxd kernel: br-lxd0: port 6(veth103185f9) entered blocking state
Oct 30 22:55:35 aqui-vm-lxd kernel: br-lxd0: port 6(veth103185f9) entered disabled state
Oct 30 22:55:35 aqui-vm-lxd kernel: device veth103185f9 entered promiscuous mode
Oct 30 22:55:36 aqui-vm-lxd audit[301799]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="incus-rk9-test_</var/lib/incus>" pid=301799 comm="apparmor_parser"
Oct 30 22:55:36 aqui-vm-lxd kernel: audit: type=1400 audit(1761836136.374:25): apparmor="STATUS" operation="profile_load" profile="unconfined" name="incus-rk9-test_</var/lib/incus>" pid=301799 comm="apparmor_parser"
Oct 30 22:55:36 aqui-vm-lxd kernel: physgJPJmm: renamed from veth9fbe6190
Oct 30 22:55:36 aqui-vm-lxd kernel: eth0: renamed from physgJPJmm
Oct 30 22:55:36 aqui-vm-lxd kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 30 22:55:36 aqui-vm-lxd kernel: br-lxd0: port 6(veth103185f9) entered blocking state
Oct 30 22:55:36 aqui-vm-lxd systemd-networkd[483]: veth103185f9: Gained carrier
Oct 30 22:55:36 aqui-vm-lxd kernel: br-lxd0: port 6(veth103185f9) entered forwarding state
Oct 30 22:55:36 aqui-vm-lxd kernel: Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
Oct 30 22:55:37 aqui-vm-lxd systemd-networkd[483]: veth103185f9: Lost carrier
Oct 30 22:55:38 aqui-vm-lxd kernel: br-lxd0: port 6(veth103185f9) entered disabled state
Oct 30 22:55:38 aqui-vm-lxd kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 30 22:55:38 aqui-vm-lxd kernel: br-lxd0: port 6(veth103185f9) entered blocking state
Oct 30 22:55:38 aqui-vm-lxd systemd-networkd[483]: veth103185f9: Gained carrier
Oct 30 22:55:38 aqui-vm-lxd kernel: br-lxd0: port 6(veth103185f9) entered forwarding state
So, is there anything I can do to figure out what’s behind?