moby: Sometimes a docker container gets stuck so that it can't be stopped or removed
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1fb364265a92 mediit/mongodb:stage "mongod" 22 minutes ago Up 22 minutes 0.0.0.0:49195->27017/tcp, 0.0.0.0:49196->28017/tcp mongodb
$ docker stop mongodb
Error response from daemon: Cannot stop container mongodb: no such process
FATA[0000] Error: failed to stop one or more containers
$ docker rm -f mongodb
Error response from daemon: Could not kill running container, cannot remove - no such process
FATA[0001] Error: failed to remove one or more containers
$ docker info
Containers: 14
Images: 178
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Dirs: 206
Execution Driver: native-0.2
Kernel Version: 3.13.0-32-generic
Operating System: Ubuntu 14.04.1 LTS
CPUs: 2
Total Memory: 7.704 GiB
Name: medi-it-sote
ID: GGAU:OQIH:U6ZI:TOEP:G3JX:Z5WA:D5WQ:CFPA:NLMB:F6P5:IR7I:2GTC
WARNING: No swap limit support
$ docker version
Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 5bc2ff8
OS/Arch (client): linux/amd64
Server version: 1.4.1
Server API version: 1.16
Go version (server): go1.3.3
Git commit (server): 5bc2ff8
$ uname -a
Linux medi-it-sote 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
This happens occasionally, any ideas?
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Reactions: 12
- Comments: 115 (28 by maintainers)
Guys, you are consolidating issues into one by telling they are the same issue which is OK. Then you are closing the issue complaining that there are multiple issues in one bug report.
People are looking for workarounds when they get no love in here. Closing issues without addressing the problem does not make any sense.
only sudo /etc/init.d/docker restart helps or docker-machine restart default, for those in trouble here 😉
I am experiencing this issue once out of two times under 4.2.0-27-generic #32~14.04.1-Ubuntu. It could never be reproduced under Docker for Mac which I find quite interesting, may point to Ubuntu. Both builds are like below.
Seems to be the same as: https://github.com/docker/docker/issues/22312 Which has a PR merged. So fingers crossed for next release.
In the mean time, I found that stopping the docker daemon, then manually deleting the container folders allowed me to continue without destroying the vm. E.g.
Having the same issue with Docker version 1.13.0, build 49bf474, ubuntu 14.04. After the container been running for a long period of time.
I think we should close this. Like @thaJeztah said, this is a collection of unrelated problems. There are people commenting with their
docker infobut I have no idea which problem they are even referring to as the error message from original report was gone already inv1.7.0. #22423 matches most of the descriptions in here and is fixed withv1.12. If you have trouble removing a container, please start a new issue, include information about the specifics of your container and daemon logs. If it is a hang then sendSIGUSR1signal to docker daemon and include it in the issue report as suggested in https://github.com/docker/docker/issues/10589#issuecomment-234693470 .worth knowing - if you are running an ENTRYPOINT script … the script will work with the shebang #!/bin/bash -x BUT will stop the container from stopping with #!/bin/bash -xe hope that helps someone
Same issue with the official
icinga/icinga2image. The only way to stop the container was to reboot the machine.