Strange behavior on Container Startup on IncusOS

IncusOS
,
1

Hey there,

I’m currently testing IncusOS (version=202512112135) in my homelab. I am coming from proxmox and wanted to try out Incus with IncusOS.

I am running currently 13 Containers and 3 VM on the Incus host.

I have noticed that when several containers are running (approx. 10), I cannot start any more containers. If I set them to autostart and reboot, more containers come up, but not all of them.

I get the following error message in the containers that do not start automatically:

lxc renovate 20251213123411.385 WARN     conf - ../src/lxc/conf.c:lxc_setup_keyring:3599 - Disk quota exceeded - Failed to create kernel keyring
lxc 20251213123411.524 ERROR    af_unix - ../src/lxc/af_unix.c:lxc_abstract_unix_recv_fds_iov:218 - Connection reset by peer - Failed to receive response
lxc 20251213123411.524 ERROR    commands - ../src/lxc/commands.c:lxc_cmd_rsp_recv_fds:128 - Failed to receive file descriptors for command "get_state"

Per default there is not limit of running containers at the host. I tried to set it to 50, but it does not help.

Furthermore, it is sometimes the case that the network interface that I have set in the container configuration is displayed as down (within the container) when the container is started. When manually starting up within the container, the container only gets an IPv6 address and no IPv4. Restarting IncusOS usually fixes the problem.

Container config:

devices:
  eth0:
    hwaddr: BC:24:11:4E:54:A8
    nictype: bridge
    dparent: enp4s0
    type: nic

42: eth0@if43: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether bc:24:11:4e:54:a8 brd ff:ff:ff:ff:ff:ff link-netnsid 0

Thank you in advance!

2

That sounds like "Too many open files" with LXC containers · Issue #693 · lxc/incus-os · GitHub

3

We’re preparing an update now which will bring in the latest kernel bugfix release as well as a refreshed Incus package which should fix that bug.

4

That sound really similar to the observed issue. Thank you very much. I will test it, as soon it is available.

5

Can confirm, both issues are fixed with the newest version. Awesome work, overall!

1 Like