on a ubuntu 24.04.4 vm (running on ESX) I purged all incus packages, wiped the zfs device and reinstalled latest incus without any error but once I try to start a new container this container fails to start:
incus launch images:ubuntu/24.04 test
Launching test
Error: Failed instance creation: Failed to run: /opt/incus/bin/incusd forkstart test /var/lib/incus/containers /run/incus/test/lxc.conf /var/log/incus/test: exit status 1
incus info --show-log test
Name: test
Description:
Status: STOPPED
Type: container
Architecture: x86_64
Created: 2026/05/28 13:52 UTC
Last Used: 2026/05/28 13:52 UTC
Log (lxc.log):
lxc test 20260528135241.413 ERROR utils - ../src/lxc/utils.c:run_buffer:569 - Script exited with status 32
lxc test 20260528135241.413 ERROR conf - ../src/lxc/conf.c:lxc_setup:3845 - Failed to run mount hooks
lxc test 20260528135241.413 ERROR start - ../src/lxc/start.c:do_start:1466 - Failed to setup container "test"
lxc test 20260528135241.413 ERROR sync - ../src/lxc/sync.c:sync_wait:34 - An error occurred in another process (expected sequence number 4)
lxc test 20260528135241.416 ERROR network - ../src/lxc/network.c:lxc_netdev_restore_altnames:1422 - Invalid argument - Failed to get altnames for interface "vethcb7baebf"
lxc test 20260528135241.416 WARN network - ../src/lxc/network.c:lxc_delete_network_priv:3940 - Failed to restore altnames for interface with index 0 and initial name "vethcb7baebf"
lxc test 20260528135241.416 WARN network - ../src/lxc/network.c:lxc_delete_network_priv:3945 - Failed to rename interface with index 0 from "physbwonOD" to its initial name "vethcb7baebf"
lxc test 20260528135241.416 ERROR lxccontainer - ../src/lxc/lxccontainer.c:wait_on_daemonized_start:837 - Received container state "ABORTING" instead of "RUNNING"
lxc test 20260528135241.416 ERROR start - ../src/lxc/start.c:__lxc_start:2288 - Failed to spawn container "test"
lxc test 20260528135241.416 WARN start - ../src/lxc/start.c:lxc_abort:1229 - No such process - Failed to send SIGKILL via pidfd 17 for process 4201
lxc 20260528135241.514 ERROR af_unix - ../src/lxc/af_unix.c:lxc_abstract_unix_recv_fds_iov:218 - Connection reset by peer - Failed to receive response
lxc 20260528135241.514 ERROR commands - ../src/lxc/commands.c:lxc_cmd_rsp_recv_fds:128 - Failed to receive file descriptors for command "get_init_pid"
found out the reason:
this ubuntu server was setup with systemd-network. Once switching back to default netplan network config incus behaves as expected. So either the systemd-network config has incompatible parts or incus is not compatible with network config done by systemd.
Could some tell me please if network config should be possible by systemd with incus in general?
I try to decipher the systemd config and will report back âŠ
Iâm not familiar with how modern(ish) Ubuntu configures its networking, but Incus is very much compatible with systemd-networkd â itâs how IncusOS (based on Debian trixie) configures all of its networking.
If your system is running in the DMZ and processes high sensitive data, there is usually no reason to allow ptrace at all. Best is to disable it completely (kernel.yama.ptrace_scope = 3).
Just to add, my Nvidia containers wonât start as well. Removal of Nvidia runtime works, but eventually had to downgrade to last 7.0 release to get this functionality back.
