Incus fails to allow forwarded ports on Void due to systemd expectations.... #51015
Description
Is this a new report?
Yes
System Info
Void
Package(s) Affected
incus
Does a report exist for this bug with the project's home (upstream) and/or another distro?
tldr; the solution is to run:
mkdir /sys/fs/cgroup/systemd
mount -t cgroup -o none,name=systemd systemd /sys/fs/cgroup/systemd
and then you can start your containers......I guess incus on void is expecting systemd mounts in the cgroup
Classic case of devs only making things catered to ubuntu/debian builds
Reporting this here, doubt anyone is going to fix it.
Cheers
Expected behaviour
Containers running
Actual behaviour
Containers wont run and bind to forwarded ports.
Steps to reproduce
read the linked issue