DevKinsta Repeatedly Does Not Load

[natasha_nightshift (Natasha)]

Hey support,

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.

main.log (32.3 KB)

[Andrew]

Hi @natasha_nightshift! Thank you for reaching out to us on the forums.

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.

Best regards

[Andrew]

Hello again,

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.

We look forward to hearing from you!

[natasha_nightshift (Natasha)]

Hi Andrew,

This was the output when I run docker info:

You have new mail.
➜  ~ docker info
Client:
 Version:    27.3.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.17.1-desktop.1
    Path:     /Users/[USERNAME]/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.7-desktop.1
    Path:     /Users/[USERNAME]/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.37
    Path:     /Users/[USERNAME]/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.15
    Path:     /Users/[USERNAME]/.docker/cli-plugins/docker-desktop
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/[USERNAME]/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.27
    Path:     /Users/[USERNAME]/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/[USERNAME]/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.3.0
    Path:     /Users/[USERNAME]/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/[USERNAME]/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.14.0
    Path:     /Users/[USERNAME]/.docker/cli-plugins/docker-scout

Server:
 Containers: 5
  Running: 5
  Paused: 0
  Stopped: 0
 Images: 7
 Server Version: 27.3.1
 Storage Driver: overlayfs
  driver-type: io.containerd.snapshotter.v1
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 472731909fa34bd7bc9c087e4c27943f9835f111
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.10.11-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 8
 Total Memory: 7.654GiB
 Name: docker-desktop
 ID: bf5ab52a-e159-49b5-8df8-769fa352fff2
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Labels:
  com.docker.desktop.address=unix:///Users/[USERNAME]/Library/Containers/com.docker.docker/Data/docker-cli.sock
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: daemon is not using the default seccomp profile

If I run ls -l /var/run/docker.sock it outputs this:
ls: /var/run/docker.sock: No such file or directory

[Andrew]

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!

Best regards

[natasha_nightshift (Natasha)]

Hi Andrew,

Thank you for your help!

Yes, still seeing ‘no such file or directory’:

• ls -l /var/run/docker.sock → ls: /var/run/docker.sock: No such file or directory

When I run the command you noted, here is what happened when I try running ls -l /var/run/docker.sock again:

• sudo ln -s "$HOME/.docker/run/docker.sock" /var/run/docker.sock → lrwxr-xr-x 1 root daemon 47 30 Dec 13:49 /var/run/docker.sock -> /Users/[USERNAME]/.docker/run/docker.sock

(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?

[Adrian_L (Adrian Lorica)]

Hi @natasha_nightshift

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.

[natasha_nightshift (Natasha)]

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.

[Adrian_L (Adrian Lorica)]

That’s strange. You can also check if you notice this warning at the top section of your Docker Desktop.

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.

Docker Version: 4.37.2 (latest)
DevKinsta: 2.13.4 (latest)

Additionally, one of my colleagues tried but couldn’t replicate this issue on her Mac. Regrettably, this seems to be a local issue on your machine.

[natasha_nightshift (Natasha)]

Interesting.

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.

Thank you for the support.