mongo: Can't stop mongo docker container

I am having trouble to stop running mongo docker container. I got following message when I run “docker stop [container name]”, Anybody having same issue? the mongodb itself seems to be working fine. just can’t stop the container… so I have to restart VM in order to stop the mongo container. I am using version 2.6 Dockerfile and build and run with docker-compose.

ERROR: for [container name]  HTTPSConnectionPool(host='X.X.X.X', port=2376): Read timed out. (read timeout=70)
ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).

It seems it is related to http connection error with port 2376, but I couldn’t figure out why it is happening, other container built and run by docker-compose works just fine and stopped precisely.

About this issue

Original URL
State: closed
Created 9 years ago
Comments: 28 (6 by maintainers)

Commits related to this issue

Use specific stemcell version We can't use newer stemcell due to [issue with Docker and Linux kernel] (https://github.com/docker-library/mongo/issues/71). — committed to trustedanalytics/docker-services-boshworkspace by mstrzele 8 years ago
Use specific stemcell version We can't use newer stemcell due to [issue with Docker and Linux kernel] (https://github.com/docker-library/mongo/issues/71). — committed to trustedanalytics/cf-boshworkspace by mstrzele 8 years ago

Most upvoted comments

Closing old issue, this should be fixed by using a newer docker daemon (1.10+). Feel free to comment on further troubleshooting if you feel this was closed in error or on the solution to help users running into the same problem.

yosifkit on Aug 28, 2017

Same problem on Ubuntu with mongo:2.6:

$ docker --version
Docker version 1.9.1, build a34a1d5
$ docker-compose --version
docker-compose version 1.5.2, build 7240ff3

My mongo definition on docker-compose.yml:

mongo:
  image: mongo:2.6
  volumes:
    - ./docker/conf/mongodb.yml:/etc/mongodb.conf:ro
  command: mongod --config /etc/mongodb.conf

The mongodb.yml file:

storage:
  journal:
    enabled: false

Sometime, mongo process got 100% CPU usage and can be stopped. I tried (in order):

docker-compose stop (^C)
sudo service docker stop # Docker service is stopped, mongo container still running.
kill -9 <mongo_process>

This container is like Chuck Norris.

Let me know if you need additional information.

soullivaneuh on Jan 19, 2016

Any ideas on reproducing this so that we can find the cause? Are you all on OSX? Is there a common docker version (docker info)? Maybe a common docker-compose configuration? Has it happened on other containers besides mongo?

yosifkit on Jan 5, 2016