Running docker inside a debian systemd-nspawn container

[r00igev@@r]

I'm struggling to figure out a way to make docker working inside a systemd-nspawn container.

I keep on encounter various cgroup / cgroup v2 errors no matter how I slice and dice it.

Any nspawn experts out there?

 

[Nod]

Would this help?

systemd-nspawn - ArchWiki

 

[Gravedigger]

@r00igev@@r Are you sure that the kernel fully supports the cgroup stuff the container is looking for?

How can I check if cgroups are available on my Linux host?

Is there a command to check if the container services are running on a Linux system? Someone suggested unshare but I am not sure if that is the best way to do it.

unix.stackexchange.com

I had to recompile a kernel for a device a while ago, with some freezer cgroup feature, for the software on it to work properly.

 

[r00igev@@r]

@r00igev@@r Are you sure that the kernel fully supports the cgroup stuff the container is looking for?

How can I check if cgroups are available on my Linux host?

Is there a command to check if the container services are running on a Linux system? Someone suggested unshare but I am not sure if that is the best way to do it.

unix.stackexchange.com

I had to recompile a kernel for a device a while ago, with some freezer cgroup feature, for the software on it to work properly.

Latest bullseye and kernel.

CONFIG_CGROUPS=y
CONFIG_BLK_CGROUP=y
CONFIG_CGROUP_WRITEBACK=y
CONFIG_CGROUP_SCHED=y
CONFIG_CGROUP_PIDS=y
CONFIG_CGROUP_RDMA=y
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_HUGETLB=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_CGROUP_PERF=y
CONFIG_CGROUP_BPF=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_SOCK_CGROUP_DATA=y
# CONFIG_BLK_CGROUP_IOLATENCY is not set
# CONFIG_BLK_CGROUP_IOCOST is not set
# CONFIG_BFQ_CGROUP_DEBUG is not set
CONFIG_NETFILTER_XT_MATCH_CGROUP=m
CONFIG_NET_CLS_CGROUP=m
CONFIG_CGROUP_NET_PRIO=y
CONFIG_CGROUP_NET_CLASSID=y

 

[r00igev@@r]

Would this help?

systemd-nspawn - ArchWiki

I've used exactly that as well and no dice.

 

[Gravedigger]

I've used exactly that as well and no dice.

Eish. Does dmesg tell you anything?
I found this command useful: dmesg --follow
After executing that command in a separate shell/window/session, try to start the service, and check the logs.
There must be something missing or some permission/service not present?