I’m having a problem with containers which occasionally stuck in “created” state:
fe6f02ec9fb8 a8237729a802 "my_command" 2 days ago Created my_container
I cannot do anything with it, literally.
docker rm -f,
docker logs fe6f02ec9fb8 commands don’t work, they just hang without any action and no output.
docker container prune --force has no effect and the container still exists.
After my investigation I realized, that the problem is with:
root 27982 29598 0 Jan25 ? 00:00:15 docker-untar /var/lib/docker/aufs/mnt/5ebfd46f44cb0e5c5a33bccdd96438914a1d8b375d6aea0a168877795d526b9c/tmp/local_files
Killing this process unfortunatelly doesn’t fix the problem, and restart of Docker’s daemon is required - which is an action I want to avoid on my production server, but because of that it is needed 1-2 times per week. That’s not good.
After Docker restart the container’s state is changed (to “Removing” AFAIR, I can’t confirm it now), but still cannot be removed until I unmount
/var/lib/docker/aufs/mnt/5ebfd46f44cb0e5c5a33bccdd96438914a1d8b375d6aea0a168877795d526b9c. Then I’m able to remove this dangling container.
What can I do to avoid Docker restarts? Is this a bug in Docker?
Thanks in advance for your help.
$ docker version Client: Version: 18.06.0-ce API version: 1.38 Go version: go1.10.3 Git commit: 0ffa825 Built: Wed Jul 18 19:11:02 2018 OS/Arch: linux/amd64 Experimental: false Server: Engine: Version: 18.06.0-ce API version: 1.38 (minimum version 1.12) Go version: go1.10.3 Git commit: 0ffa825 Built: Wed Jul 18 19:09:05 2018 OS/Arch: linux/amd64 Experimental: false