Container does not start at all.

[Likqez]

Hello,

whenever pterodactyl tries to start a container, I get the following error. I'm on a Debian machine without virtualization.

Details

likqez@havana:~$ docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc., v0.10.2)
  compose: Docker Compose (Docker Inc., v2.16.0)
  scan: Docker Scan (Docker Inc., v0.23.0)

Server:
 Containers: 10
  Running: 9
  Paused: 0
  Stopped: 1
 Images: 23
 Server Version: 20.10.5+dfsg1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runtime.v1.linux runc io.containerd.runc.v2
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 1.4.13~ds1-1~deb11u3
 runc version: 1.0.0~rc93+ds1-5+deb11u2
 init version:
 Security Options:
  apparmor
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.10.0-21-amd64
 Operating System: Debian GNU/Linux 11 (bullseye)
 OSType: linux
 Architecture: x86_64
 CPUs: 12
 Total Memory: 62.59GiB
 Name: havana.pluginstube.dev
 ID: UCOG:LEJU:OBNR:UHAX:WOR4:MQEA:3AQ4:W4YX:HLKL:KI7Z:PTK6:WPSJ
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

likqez@havana:~$ systemd-detect-virt
none

Error Event [c1ef3f3c-82cd-413c-ba6b-a531c0bac03d]: environment/docker: failed to start container: Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: process_linux.go:458: setting cgroup config for procHooks process caused: openat2 /sys/fs/cgroup/system.slice/docker-66fac8e31a42c41424fb93f2c9105fa0291270f0ec620185eac0f797b6381c87.scope/io.bfq.weight: no such file or directory: unknown

I tried to:

• use different images, e.g. eclipse-temurin:19-jre-alpine
• update my kernel
• added systemd.unified_cgroup_hierarchy=0 to GRUB_CMDLINE_LINUX in /etc/default/grub
• tried running the same images via docker-cli (worked).

But the issue persists. Normal containers are running as usual. Only the ones created by wings are not able to start.

Anyone got any ideas how to fix this?