How to gracefully shut down monogodb 0.8 running in docker

mongodb docker shutdown
canadadry picture canadadry · Feb 18, 2014 · Viewed 13.6k times · Source

I am starting mongodb via the ENTRYPOINT config in a docker file. It works fine. However, when I execute:

docker stop <containerid>

it seems to be sending a SIGTERM to the process. Which means the mongod.lock file is not cleared. How can I gracefully shutdown a running docker container so that the right signals are sent to the process running inside docker ?

Answer

creack picture creack · Feb 18, 2014

I am not sure to understand. docker stop <id> will indeed send a SIGTERM. This is by design. If the process didn't shutdown properly within the timeout (default is 10 sec), then a SIGKILL is emitted.

At the moment, we do have some issue with the signal propagation though. It is due to the pid namespace and the fact that the process has a pid 1. This should get fixed soon with the new execution plugins.

Related questions

How to create a DB for MongoDB container on start up?

I am working with Docker and I have a stack with PHP, MySQL, Apache and Redis. I need to add MongoDB now so I was checking the Dockerfile for the latest version and also the docker-entrypoint.sh file from the …

Read More
How can I wait for a docker container to be up and running?

When running a service inside a container, let's say mongodb, the command docker run -d myimage will exit instantly, and return the container id. In my CI script, I run a client to test mongodb connection, right after running the …

Read More
How to connect to MongoDB running in Docker container?

I'm running a Docker container on MacOS that starts a Postgres server and MongoDB server as follows: docker run -p 80:80 -p 27017:27017 dockertest * Starting PostgreSQL 9.3 database server ...done. * Starting database mongodb ...done. The output shows that the MongoDB server is started …

Read More