Open ghost opened 3 years ago
From the output of docker version
and docker info
, I think this is a build of docker that's maintained by Amazon (we don't build packages for Amazon Linux currently), and both Docker and Containerd are quite outdated (note that containerd 1.3 reached EOL). Are you able to reproduce this on a current version of docker and containerd?
seems like #42437 has the same issue with newer docker/containerd versions
Hi, I have same issue, this is my environment:
Client: Docker Engine - Community Version: 20.10.6 API version: 1.41 Go version: go1.13.15 Git commit: 370c289 Built: Fri Apr 9 22:47:17 2021 OS/Arch: linux/amd64 Context: default Experimental: true
Server: Docker Engine - Community Engine: Version: 20.10.6 API version: 1.41 (minimum version 1.12) Go version: go1.13.15 Git commit: 8728dd2 Built: Fri Apr 9 22:45:28 2021 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.4 GitCommit: 212e8b6fa2f44b9c21b2798135fc6fb7c53efc16 runc: Version: 1.1.1 GitCommit: v1.1.1-0-g52de29d docker-init: Version: 0.19.0 GitCommit: de40ad0
Description Container does not respond to external commands when killed by OOM killer.
Steps to reproduce the issue:
Describe the results you received: Container did not restart automatically after killed by OOM killer. Also, the container stopped responding to external commands.
Describe the results you expected: Container should restart automatically after killed by OOM killer.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
OS
Docker container was killed by OOM Killer
after that, the container becomes unresponsive to commands, Tried
all commands are unresponsive, and after restarting the host os, the containers were started.