Docker db container running. Another process with pid <id> is using unix socket file

I solved this issue by doing the following command:

docker-compose down --volumes

And then:

sail up --build

https://rawbinn.com/blog/mysql-not-starting-on-docker

Thanks to halcyon comment:

If you use docker desktop. In menu → "Volumes" → click your volume name → select "data" tab. And here remove “mysql.sock.lock” Now mysql works.

I was facing the same issue. Following are the steps that I tried to resolve this issue -

• Firsly, stop your docker service by using following command - "sudo service docker stop"

• Now,get into the docker folder in my Linux system using the following path - /var/lib/docker.

• Then within the docker folder you need to get into the volumes folder. This folder contains the volumes of all your containers (memory of each container) - cd /volumes

• After getting into volumes do 'sudo ls' you will find multiple folders with hash names. These folders are volumes of your containers. Each folder is named after its hash (You need to inspect your docker container and get the hash of your container volume. For this, you need to do the following steps -

Run command "docker inspect 'your container ID' ".

Now you will get a JSON file. It is the config file of your docker container.

Seach for Mounts key within this JSON file. In Mounts, you will get the Name(hash) of your volume. (You will also get the path of your volume within the Mounts. Within Mounts "Name" key is your volume name and "Source" is the path where your volume is located.)).

• Once you get the name of your volume you can go within your volume folder and within this folder you will find "_data" folder. Get into this folder.

• Finally within "_data" folder use sudo ls command and you will find a folder with the name mysql.sock.lock. Remove this folder By "rm -f mysql.sock.lock".

• Now restart your docker service and then start your docker container. It will start working.

Note- Use sudo in each command while you are in the docker container folder.

Just faced same problem.

After many research, summary of my solution:

1. Find host location of docker files

   $ docker inspect <container_name> --> Mounts.Source section

In my case, it was /var/snap/docker/common/.../_data

As root, you can ls -l that directory and see the files that are preventing your container from starting, the socket mysql.sock and the file mysql.sock.lock

Simply delete them as root ($ sudo rm /var/snap/.../_data/mysql.sock*) and start your docker container.

NOTE: be sure you don't have any other mysql.sock... files than those two. In that case don't use wildcar (*), delete each of them individually.

Hope this helps.

You should make sure the socket file have been deleted before you start mysql.Check my.cnf(/etc/mysql/my.cnf) file to get the path of socket file. find sth like this socket = /var/run/mysqld/mysqld.sock.And delete the .sock.lock file as well.

I had the same problem and got rid of it in an easy and mysterious way.

First I have noticed that I am unable to start mysql_container container. Running docker logs mysql_container indicated exactly the same problem as described repeating for few times.

I wanted to get a look around by running the container in an interactive mode by docker start -i mysql_container from one bash window while running things like docker exec -it mysql_container cat /etc/mysql/my.cnf in another.

I have done that and was very surprised to see that this time the container started successfully. I cannot understand why. I can only guess that starting an interactive mode together with running subsequent docker exec commands slowed down init process and some another process had a bit more time to remove its locks.

Hope that helps anybody.

This is a glitch with docker.

Execute following commands:

docker stop $(docker ps -a -q)
docker rm $(docker ps -a -q)

This will stop all containers and remove them.

After this it should work just fine.

Generally this means a previously-running MySQL instance has placed a lock on the DB via the filesystem.

If you're sure no instances are running, you can delete the dangling locks that remain and no conflict error will appear.

As per shubham tak's answer you can remove these locks that are persisting on the Docker virtual filesystem by removing them from the host computer's filesystem directly.

Or, you can use the Docker CLI to blast it all away and start fresh:

docker system prune
docker volume prune

And then try again.

I faced the same problem.

Docker caches it's images for faster container composing.

I found, by removing the cached image of 'mysql/mysql-server:8.0' and then trying 'sail up'/'compose up' again. Docker downloads a fresh images which solved the socket problem.

ERROR MESSAGE:
Another process with pid 62 is using unix socket file.
Unable to setup unix socket lock file.

Lesson learned: Don't doubt yourself and Try again from the start.

Keep Coding Beauties ;)

I solved this by changing the image I was pulling from docker-compose.yml

There are also other ways to resolve this, such as deleting mysql.sock

You can follow this commands to verify if the files exist:

sudo ls /var/lib/docker/volumes/web_sail-mysql/_data

Case yes:

sudo rm /var/lib/docker/volumes/web_sail-mysql/_data/mysql.sock
sudo rm /var/lib/docker/volumes/web_sail-mysql/_data/mysql.sock.lock