background: Fedora 32 version of the operating system, running the container times error
[root@Fedora4 ~]# docker run -d -p 1001:80 --name blog1 tutum/wordpress
97da5679108744a76fda3e171d49304cce059091ee321d6fd08c8d61a4300ee8
docker: Error response from daemon: OCI runtime create failed: this version of runc doesn't work on cgroups v2: unknown.
try again to start the container as well:
[root@Fedora4 ~]# docker start blog1
Error response from daemon: OCI runtime create failed: this version of runc doesn't work on cgroups v2: unknown
The
solution is configured as follows:
[root@Fedora4 ~]# grubby --update-kernel=ALL --args="systemd.unified_cgroup_hierarchy=0"
[root@Fedora4 ~]# reboot
after restart, the container can be started normally.
[root@Fedora4 ~]# docker start blog1
blog1
[root@Fedora4 ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
97da56791087 tutum/wordpress "/run.sh" 4 minutes ago Up 11 seconds 3306/tcp, 0.0.0.0:1001->80/tcp blog1
Reference documents:
https://jaranguda.com/fedora-docker-this-version-of-runc-doesnt-work-on-cgroups-v2/
Read More:
- Docke Run: response from daemon: OCI runtime create failed: container with id exists:XXX:unknown
- The docker runtime container reported an error: error response from daemon: OCI runtime create failed
- Error response from daemon: OCI runtime create failed: container_linux.go:380
- Error response from daemon: OCI runtime exec failed: exec failed: container_linux.go:345:
- Docker start error: failed to start docker application container engine.
- Error: cudaGetDevice() failed. Status: CUDA driver version is insufficient for CUDA runtime version
- Error: (serious: a child container failed during start) (server component failed to start so Tomcat is unable)
- One of the configured repositories failed (Unknown), and yum doesn’t have enough cached data to cont
- Solve the problem that idea’s. Gitignore doesn’t work sometimes
- Error running docker container: starting container process caused “exec: \“python\“: executable file
- A child container failed during start Tomcat error prompt
- Yarn: runtime.ContainerExecutionException : launch container failed
- A child container failed during start
- Error — failed to start docker container, error iptables — wait – t nat
- An error occurred when starting Tomcat in Eclipse: the sub container failed to start
- Docker starts MySQL container and reports an error driver failed programming external connectivity on endpoint mysq
- Solve selenium error — unknown error: devtoolsactivport file doesn’t exist
- cadvisor Failed to start container manager: inotify_add_watch /sys/fs/cgroup/cpuacct,cpu: nosuchfile
- Caused by: org.apache.catalina.LifecycleException: A child container failed during start
- [Solved] selenium.common.exceptions.WebDriverException: Message: unknown error: DevToolsActivePort file doesn