Answers: <p>This is probably because Docker Desktop version 4.18+ doesn't create the default Docker socket <code>/var/run/docker.sock</code> anymore.</p>
  <p>The reasoning is on the official docs: <a href="https://docs.docker.com/desktop/mac/permission-requirements/" rel="noreferrer">https://docs.docker.com/desktop/mac/permission-requirements/</a></p>
  <p>If you want to have the default socket back, you should open your Docker Desktop, go to <code>Settings -&gt; Advanced -&gt; Allow the default Docker socket to be used</code> and press <code>Apply &amp; restart</code>.</p>
  
Answers: CC BY-SA 4.0
Answers: 2023-06-05T18:52:56.920Z
Answers: Amazing, this is exactly it, thank you!
Answers: Seth Lutske
Answers: CC BY-SA 4.0
Answers: 2023-06-05T17:38:14.983Z
Answers: 2023-06-05T17:38:14.983Z
Answers: Lev Romanov
Body: <p>I am very fond of <a href="https://github.com/bcicen/ctop" rel="nofollow noreferrer">ctop</a>, a command-line manager for docker containers.  I recently upgraded my docker to v23.0.5 on mac OSX Ventura 13.4 (Intel chip). After doing so, and running ctop, I get the daemon erroring out with this message:</p>
  <blockquote>
  <p>Get &quot;http://unix.sock/info&quot;: dial unix /var/run/docker.sock: connect: no such file or directory<br />
  <a href="https://i.sstatic.net/LVYNY.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/LVYNY.png" alt="enter image description here" /></a></p>
  </blockquote>
  <p>I checked and it is indeed true that there is no <code>docker.sock</code> there with the new version of docker.  Checking another machine running docker v20, docker.sock is right there in that location.  I figured maybe with the new version, that file has a new home.  I did manage to find a docker.sock at <code>Users/sethlutske/.docker/run/docker.sock</code>, so I set the environment variable <code>export DOCKER_HOST=/Users/sethlutske/.docker/run/docker.sock</code> as recommended in the ctop <a href="https://github.com/bcicen/ctop/blob/master/_docs/connectors.md" rel="nofollow noreferrer">docs on customization</a>, but then running <code>ctop</code> gives me another error:</p>
  <blockquote>
  <p>Get &quot;tcp:///Users/sethlutske/.docker/run/docker.sock/info&quot;: unsupported protocol scheme &quot;tcp&quot;</p>
  </blockquote>
  <p>What has changed in the version of docker?  ctop isn't exactly maintained any more, but ctop really isn't the issue considering it allows customization of where to find the docker socket.  I'm trying to understand why the docker docs say that the docker socket should be at this location, but its somewhere else, and seems to be different than what ctop expects?</p>
  
Tags: <docker>
Title: ctop does not work with latest version of docker: Get "http://unix.sock/info": dial unix /var/run/docker.sock: connect: no such file or directory
UserDisplayName: Seth Lutske
ThreadText: # ctop does not work with latest version of docker: Get "http://unix.sock/info": dial unix /var/run/docker.sock: connect: no such file or directory
  
  (Asked by: username_0 on 2023-05-31)
  
  I am very fond of [ctop](https://github.com/bcicen/ctop), a command-line manager for docker containers. I recently upgraded my docker to v23.0.5 on mac OSX Ventura 13.4 (Intel chip). After doing so, and running ctop, I get the daemon erroring out with this message:
  
  > Get "http://unix.sock/info": dial unix /var/run/docker.sock: connect: no such file or directory  
  > [![enter image description here](https://i.sstatic.net/LVYNY.png)](https://i.sstatic.net/LVYNY.png)
  
  I checked and it is indeed true that there is no `docker.sock` there with the new version of docker. Checking another machine running docker v20, docker.sock is right there in that location. I figured maybe with the new version, that file has a new home. I did manage to find a docker.sock at `Users/username_0/.docker/run/docker.sock`, so I set the environment variable `export DOCKER_HOST=/Users/username_0/.docker/run/docker.sock` as recommended in the ctop [docs on customization](https://github.com/bcicen/ctop/blob/master/_docs/connectors.md), but then running `ctop` gives me another error:
  
  > Get "tcp:///Users/username_0/.docker/run/docker.sock/info": unsupported protocol scheme "tcp"
  
  What has changed in the version of docker? ctop isn't exactly maintained any more, but ctop really isn't the issue considering it allows customization of where to find the docker socket. I'm trying to understand why the docker docs say that the docker socket should be at this location, but its somewhere else, and seems to be different than what ctop expects?
  
  **Tags:** docker
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2023-06-05. Score: 5 | Accepted answer
  
  This is probably because Docker Desktop version 4.18+ doesn't create the default Docker socket `/var/run/docker.sock` anymore.
  
  The reasoning is on the official docs: <https://docs.docker.com/desktop/mac/permission-requirements/>
  
  If you want to have the default socket back, you should open your Docker Desktop, go to `Settings -> Advanced -> Allow the default Docker socket to be used` and press `Apply & restart`.
  
  > **Comments:**
  > **username_0**: Amazing, this is exactly it, thank you!  
  
  ---
  
  