moby: OCI runtime exec failed: exec failed: cannot exec a container that has stopped: unknown
Description docker exec xxx ls: OCI runtime exec failed: exec failed: cannot exec a container that has stopped: unknown
Steps to reproduce the issue: occur very infrequently
Describe the results you received:
`docker ps` find that the container is running,
Actually the container is exited( cat /proc/${Container.State.Pid}/stat: No such file or directory )
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version
:
18.03.0-ce
Output of docker info
:
Containers: 48
Running: 11
Paused: 0
Stopped: 37
Images: 59
Server Version: 18.03.0-ce
Storage Driver: overlay2
Backing Filesystem: xfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: syslog
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: cfd04396dc68220d1cecbe686a6cc3aa5ce3667c
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: 949e6fa
Security Options:
seccomp
Profile: default
Kernel Version: 4.16.6-1.el7.elrepo.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 62.91GiB
...
Live Restore Enabled: false
Additional environment details (AWS, VirtualBox, physical, etc.):
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 5
- Comments: 21 (8 by maintainers)
I also see this error, any updates?
Happened to us too, After OOM killer.
docker inspect: