I’ve left so many logs I’m beginning to develop a deep frustration with DevKinsta as a tool. I’ve transitioned each new client to Kinsta, because when DevKinsta first launched I was an eager and excited early adopter, and now I’m feeling like it may have been a terrible mistake. The software is simply unreliable. I continue to run into the same issue over and over and over again.
We resolve the issue, then I restart my computer for a variety of reasons, and it’s back to the same problems.
I am sorry to hear you are experiencing this continued issue with launching DevKinsta. I understand this issue impacts your ability to use DevKinsta, and the importance of finding a solution.
I have reviewed the main log file and I do see a “[error] Error: connect ENOENT /var/run/docker.sock” error being logged. This seems to indicate that DevKinsta is having difficulty connecting to the Docker service.
We are investigating into this issue further and will be following up as soon as possible with an update. We appreciate your patience while we look into this issue further.
I do just want to confirm a few things regarding the Docker service on your Mac. If you open a Terminal session and run “docker info” is anything output? Or, does an error occur as well?
Also, within that Terminal session if you run “ls -l /var/run/docker.sock” what does the output look like? If you could please share that (redact any personal information) that would help.
Hi @natasha_nightshift! Thank you for your reply and for sharing those details.
That’s very odd when running ls -l /var/run/docker.sock that it says no file or directory is found. That would seem to indicate that the socket file is missing.
Just to confirm, if you are still seeing this file as missing if you run sudo ln -s "$HOME/.docker/run/docker.sock" /var/run/docker.sock again does it complete this time without saying the file already exists?
Please let us know the outcome of running this command. We look forward to hearing from you!
(I sent you a private message with a screenshot as well for added clarity)
When I retried DevKinsta, it worked!
Here is what I assume will happen though, I’m going to shut down my machine at some point, and when I reboot in the morning, I will run into this issue all over again. Do you have any idea what is happening on restart with my Mac?
I’m not entirely sure what’s causing the issue, but it seems another application may be conflicting with Docker Desktop. If you experience the same problem after restarting your machine, check the Notifications section in Docker Desktop for any warnings. If you see this specific warning, click on it and select “Repair.” This should help resolve the problem.
Hi Adrian,
So I wound up needing to reboot my machine, naturally. And the same thing happened. Luckily I just referred to this thread, and was able to quickly resolve it.
I checked Docker, and it does not have that notification. I still don’t know how to avoid this in the future.
I tested this on my Mac Mini M2 with the following specifications. I restarted the machine several times, but I couldn’t replicate the issue. DevKinsta still works after each restart.
So my Docker looks different than yours, but it DID have that notification, it just lived in the ‘notifications’ panel which for me appears on the right hand side. By clicking on it, it repaired my DevKinsta when I rebooted my machine.