3

I have MongoDB as docker container When I restarted the server and tried to start the container it kept restarting forever.

I got the container log as follows

enter image description here

The main problem is Failed to unlink socket file /tmp/mongodb-27017.sock Operation not permitted

I found many solutions to this problem, but all of them are based on the idea that I'm using the mongod service, which isn't my case.

I'm using a docker container and I can't run commands on this container until it is running. Sadly this error doesn't let the container start and keeps restarting.

I found the issue on the official bug tracker of MongoDB since version 3.6, but also it doesn't have any solution.

I also found a similar question on DigitalOcean support with no luck to find a solution.

Shady Mohamed Sherif
  • 13,624
  • 4
  • 40
  • 49

2 Answers2

5

Warning!! When you create a MogoDB container, You should always link the directory /data/db inside your container to be on the host using Volumes.

In case /data/db isn't linked to a volume, you will lose your data.

Try to stop the container using docker stop <container>

then remove it completely using docker rm <container>

then re-build using docker build or docker-compose build depends on your usage

Note: Whenever you remove the container it's data will be removed along with it. so make sure that you have a recent backup with the database.

Shady Mohamed Sherif
  • 13,624
  • 4
  • 40
  • 49
1

I had this problem and i'd solved with docker-compose down and then docker-compose up. This problem is probably caused because your docker container is broken

Ramon
  • 241
  • 2
  • 3
  • Warning! You will lose your data if you use docker-compose down – Ed Barahona Mar 10 '22 at 18:53
  • I will only lose the data if I hadn't link a volume from outside to inside the docker container (what is a terrible mistake if the data were important). But it's a pretty good warning, to check if the link has been done. @EdBarahona – Ramon Mar 12 '22 at 15:21