Today, when the virtual machine runs docker image, it always reports an error (the specific reason for the error remains to be analyzed). After checking the system kernel and operating system version, no result is found.
[ root@bogon ~]# cat /etc/redhat-release
CentOS Linux release 7.2.1511 (Core)
[ root@bog [ root@bogon ~]# docker version
Client:
Version: 17.12.1-ce
API version: 1.35
Go version: go1.9.4
Git commit: 7390fc6
Built: Tue Feb 27 22:15:20 2018
OS/Arch: linux/amd64
Server:
Engine:
Version: 17.12.1-ce
API version: 1.35 (minimum version 1.12)
Go version: go1.9.4
Git commit: 7390fc6
Built: Tue Feb 27 22:17:54 2018
OS/Arch: linux/amd64
Experimental: false
Error information:
[ root@bogon yum.repos .d]# docker run -it centos echo haha
docker: Error response from daemon: OCI runtime create failed: unable to retrieve OCI runtime error (open /run/docker/containerd/daemon/ io.containerd.runtime .v1.linux/moby/6602807a7f1a03689a847741b0a10171788f7bed2aa92a4dff35c429b02248d1/ log.json : no such file or directory): docker-runc did not terminate sucessfully: docker-runc: symbol lookup error: docker-runc: undefined symbol: seccomp_ version
resolvent:
Upgrade the system to 7.4
It takes a long time to execute Yum update and wait patiently.
[ root@bogon ~]# cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)
[ root@bogon ~]# docker run -it centos echo haha
haha
Another solution is to install a lower version of docker, which is highly dependent on the version of the operating system. You must pay attention to it when installing!
Foreigners interpret it as follows:
RHEL 7.2 is no longer supported and Docker does not test their release against unsupported versions. You need to upgrade your OS, preferably to 7.4, to resolve this issue.
I’ve seen a few people with similar issues in the past few days that resolved this same error message by upgrading their OS. Some of the older packages no longer work with newer docker releases. One of those problems is an outdated libseccomp: https://github.com/moby/moby/issues/35906
Read More:
- Docke Run: response from daemon: OCI runtime create failed: container with id exists:XXX:unknown
- 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:
- Fedora32 start container error – OCI runtime create failed: This version of runc doesn’t work on cgroups V2: unknown
- docker Error response from daemon: Bad response from Docker engine
- When docker creates a container command: Error response from daemon: No command specified
- Docker creation container cannot find network card: error response from daemon: network XXXX not found
- docker: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled
- [Sovled] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
- docker: Error response from daemon: driver failed programming external connectivity on endpoint
- docker: Error response from daemon: driver failed programming external connectivity on endpoint lamp
- The docker copies the win10 host file into the docker container. An error is reported: copying between containers is not supported
- Docker error response from daemon: Conflict: unable to deletexxxxx
- Yarn: runtime.ContainerExecutionException : launch container failed
- Docker start error: failed to start docker application container engine.
- Error reported when Windows builds docker image: failed to create LLB definition: 403 Forbidden
- Docker delete error response from daemon: Conflict: unable to delete xxxxx solution
- Docker starts MySQL container and reports an error driver failed programming external connectivity on endpoint mysq
- How to Fix ERROR: Couldn’t connect to Docker daemon at http+docker://localhost – is it running?
- Error response from daemon: Get https://20.0.0.100/v2/: dial tcp 20.0.0.100:443: connect: connection