moby: docker ps hangs
Description
docker ps hangs , and daemon 's stderr report :containerd: 1e4323723caff73f8a4051a4b4a90a792af44dd4daf1316e2c2e8da92e706f28:164055780a76a813fb42745d5db09458389145f4ebdcc94819e5f0ece6355726 (pid 149038) has become an orphan, killing it"
I strace containerd, and found that some file is missing,and containerd is traped into endless loop
[pid 67606] openat(AT_FDCWD, “/var/run/docker/libcontainerd/containerd/1e472e701ca7481e745a03b96003743975c20f89a4e1cf2a706946063c519a0f/75e185155278527d25b3775098d7214cf49598effcb76811ae6b8700d36b1c45/pid”, O_RDONLY|O_CLOEXEC <unfinished …>
[pid 65270] futex(0xc820358d08, FUTEX_WAKE, 1 <unfinished …>
[pid 67606] <… openat resumed> ) = -1 ENOENT (No such file or directory)
after restart dockerd,it resumes ,and everything looks fined again.
Client: Version: 1.12.2 API version: 1.24 Go version: go1.6.3 Git commit: bb80604 Built: Tue Oct 11 17:00:50 2016 OS/Arch: linux/amd64
Server: Version: 1.12.2 API version: 1.24 Go version: go1.6.3 Git commit: bb80604 Built: Tue Oct 11 17:00:50 2016 OS/Arch: linux/amd64
**Output of `docker info`:**
Containers: 12 Running: 11 Paused: 0 Stopped: 1 Images: 10 Server Version: 1.12.2 Storage Driver: aufs Root Dir: /data/docker/aufs Backing Filesystem: xfs Dirs: 163 Dirperm1 Supported: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: host null overlay Swarm: inactive Runtimes: runc Default Runtime: runc Security Options: Kernel Version: 3.10.104.xxxxxx Operating System: <unknown> OSType: linux Architecture: x86_64 CPUs: 48 Total Memory: 125.3 GiB Name: xxxxxxxxxxxxxxxxx ID: VTSE:3AJP:MWYG:XSRO:VLHA:7RUN:S5KP:SDB4:HVDP:5HT3:24XC:VW52 Docker Root Dir: /data/docker Debug Mode (client): false Debug Mode (server): false Registry: https://index.docker.io/v1/ Insecure Registries: 127.0.0.0/8
**Additional environment details (AWS, VirtualBox, physical, etc.):**
centos 6 with 3.10.x kernel version.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 15 (14 by maintainers)
@ralphtheninja it depends on how
dockerd
is started; if it’s started through systemd; throughjournalctl
, if it’s started through upstart, I think logs are in/var/log/upstart/
, and if you’re manually startingdockerd
, just pipe stdout/stderr to a file