Cgroup issues with old kernel.

[stpnwf]

Description

I would like to use an old computer as a home server by using docker. For compatibility issues I must use an old kernel: 4.4.194.
But since this old kernel does not support CGroup V2, I get errors when running any container. How can I make so that docker works as expected with my computer?

Reproduce

1. Run sudo docker pull hello-world or any other container name
2. Run sudo docker run hello-world or any other container name
3. See error:

$ sudo docker run hello-world
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: cgroup namespaces aren't enabled in the kernel: unknown.
ERRO[0001] error waiting for container: context canceled

Expected behavior

I would like for the container to run normally, as expected

docker version

Client: Docker Engine - Community
 **Version:           20.10.18**
 API version:       1.41
 Go version:        go1.18.6
 Git commit:        b40c2f6
 Built:             Thu Sep  8 23:12:05 2022
 OS/Arch:           linux/arm
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  **Version:          20.10.7**
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       b0f5bc3
  Built:            Wed Jun  2 11:56:15 2021
  OS/Arch:          linux/arm
  Experimental:     false
 containerd:
  Version:          1.6.8
  GitCommit:        9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
 runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Docker Buildx (Docker Inc., v0.9.1-docker)

Server:
 Containers: 16
  Running: 0
  Paused: 0
  Stopped: 16
 Images: 4
 Server Version: 20.10.7
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 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.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
 runc version: v1.1.4-0-g5fd4c4d
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.4.194-rk322x
 Operating System: Debian GNU/Linux 11 (bullseye)
 OSType: linux
 Architecture: armv7l
 CPUs: 4
 Total Memory: 962.3MiB
 Name: server
 ID: JXPA:DST6:SJNF:74IA:HWJT:QNYZ:MREF:7DUK:XR4D:STCY:HYM5:K46J
 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

WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No cpu shares support
WARNING: No cpuset support

Additional Info

I have downgraded to an older version of docker-ce (20.10.7). But I must be doing something wrong because docker version above says I still have version 20.10.18 installed and I still get the same error when running containers.

$ apt list --all-versions docker-ce
docker-ce/bullseye 5:20.10.21~3-0~debian-bullseye armhf [upgradable from: 5:20.10.7~3-0~debian-bullseye]
docker-ce/bullseye 5:20.10.20~3-0~debian-bullseye armhf
...
docker-ce/bullseye 5:20.10.8~3-0~debian-bullseye armhf
docker-ce/bullseye,now 5:20.10.7~3-0~debian-bullseye armhf [installed,upgradable to: 5:20.10.21~3-0~debian-bullseye]
docker-ce/bullseye 5:20.10.6~3-0~debian-bullseye armhf

Would downgrading to an older version of docker-ce fix the issue?

[thaJeztah]

closing as this this went stale; it also looks to be an issue related to the daemon, and better reported in https://github.com/moby/moby, which is where the daemon is maintained.