How did I fix «Error response from daemon: cgroups: cannot find cgroup mount destination: unknown» for Docker after switching Debian 10 from SysVinit to Systemd?

dmitrii_fediuk · September 13, 2023, 2:34pm

The best solution seems to be to upgrade Docker:

cgroups: cannot found cgroup mount destination: unknown

opened 03:39AM - 05 Feb 18 UTC

* [x] This is a bug report * [ ] This is a feature request * [x] I searched ex…isting issues before opening this one ### Expected behavior ``` docker run hello-world ``` should run normally. ### Actual behavior ``` docker run hello-world docker: Error response from daemon: cgroups: cannot found cgroup mount destination: unknown. ``` ### Steps to reproduce the behavior Install latest stable or edge builds (17.12 or 18.01), using: https://docs.docker.com/install/linux/docker-ce/ubuntu/ **Output of `docker version`:** ``` Client: Version: 18.01.0-ce API version: 1.35 Go version: go1.9.2 Git commit: 03596f5 Built: Wed Jan 10 20:11:05 2018 OS/Arch: linux/amd64 Experimental: false Orchestrator: swarm Server: Engine: Version: 18.01.0-ce API version: 1.35 (minimum version 1.12) Go version: go1.9.2 Git commit: 03596f5 Built: Wed Jan 10 20:09:37 2018 OS/Arch: linux/amd64 Experimental: false ``` **Output of `docker info`:** ``` Containers: 16 Running: 0 Paused: 0 Stopped: 16 Images: 1 Server Version: 18.01.0-ce Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: 89623f28b87a6004d4b785663257362d1658a729 runc version: b2567b37d7b75eb4cf325b77297b140ea686ce8f init version: 949e6fa Security Options: seccomp Profile: default Kernel Version: 4.4.0 Operating System: Ubuntu 16.04.3 LTS OSType: linux Architecture: x86_64 CPUs: 1 Total Memory: 512MiB Name: SRV_01 ID: BBRL:P36V:7QOO:IRBR:X2TC:UC47:4L7N:IIIQ:OLSL:KWS2:OVAZ:TKKF Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false WARNING: No cpuset support WARNING: bridge-nf-call-iptables is disabled WARNING: bridge-nf-call-ip6tables is disabled ``` **Additional environment details (AWS, VirtualBox, physical, etc.)** ``` > uname -a Linux DAAA_S1 4.4.0 #1 SMP Fri Jan 5 21:20:16 MSK 2018 x86_64 x86_64 x86_64 GNU/Linux ``` ``` > ls /sys/fs/cgroup/ beancounter cpu cpuacct freezer memory net_cls,net_prio perf_event systemd blkio cpu,cpuacct devices hugetlb net_cls net_prio pids ve ``` AppArmor is also deactivated. Running under root terminal/normal terminal returns same issue. Docker pull is working. Confirmed working under ```17.09.1~ce-0~ubuntu```

How did I upgrade Docker Client from 19 to 24 on Debian 10?