I use a fresh Void Linux system, and just recently installed incus and incus-client v6.3.0.
At first I managed to create and run a Debian container, then imported another Debian container that I exported from my older incus, after editing backup/index.yaml and backup/container/backup.yaml to fit the current bridge name, etc.
They worked fine, until after a reboot, they do nothing anymore when I incus start my-container-name. The command returns with success exit status (0), but incus list shows that all containers are stopped.
I don’t know how to troubleshoot, or what logs to see (or even how to see them). Can someone please help?
tail -f /var/log/incus/my-container-name/console.log shows this, when I try to start the container:
Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted
[!!!!!!] Failed to mount API filesystems.
Exiting PID 1...
tail: console.log: file truncated
Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted
[!!!!!!] Failed to mount API filesystems.
Exiting PID 1...
Yeah, you need to have the name=systemd cgroup mounted on your system.
I remember someone else running into that not too long ago and there was some documentation that existed telling Void folks what to do to either move to cgroup2 or get the named systemd cgroup mounted on their host.