Cannot connect to the Docker daemon on macOS

Question

I normally prefer to manage my apps on my OSX with brew  I am able to install docker  docker-compose and docker-machine  docker --version Docker version 17 05 0-ce  build 89658be docker-compose --version docker-compose version 1 13 0  build unknown docker-machine --version docker-machine version 0 11 0  build 5b27455   I did not download and run  Docker for Mac  app   However when I try to run   gt  docker run -d -p 80 80 --name webserver nginx docker  Cannot connect to the Docker daemon at unix    var run docker sock  Is the docker daemon running   See  docker run --help     I have already checked the sock file  ls -lah  var run docker sock  var tmp docker sock ls   var run docker sock  No such file or directory ls   var tmp docker sock  No such file or directory   I have also tried this proposed solution  Mac OS X sudo docker Cannot connect to the Docker daemon  Is the docker daemon running on this host   But I got this error message     eval   docker-machine env default  Host does not exist   default    Is it possible to get a docker service to run by command line tools

User · Answer

You should execute script for install docker and launch it from command line:

brew install --cask docker
sudo -H pip3 install --upgrade pip3
open -a Docker
docker-compose ...

after that docker-compose should work

User · Answer

Try this to create default   docker-machine create default

User · Answer

Install minikube and come join the dark side   https   kubernetes io docs tasks tools install-minikube     bash --version GNU bash  version 5 0 3 1 -release  x86 64-apple-darwin18 2 0  Copyright  C  2019 Free Software Foundation  Inc  License GPLv3   GNU GPL version 3 or later  lt http   gnu org licenses gpl html gt    eval   minikube docker-env     docker run --rm -v   PWD   local swaggerapi swagger-codegen-cli generate     -i  local swagger json     -l python     -o  local test   main  INFO io swagger parser Swagger20Parser - reading from  local swagger json  main  WARN io swagger codegen DefaultGenerator -  host  not defined in the spec  Default to  localhost     Works great on Macbook Pro 2018 with bash v5  No need to install all the other docker nonsense these days IMO  The VM and install script that comes with minikube can replace docker machine from my experience

User · Answer

On a supported Mac  run  brew install --cask docker  Then launch the Docker app  Click next  It will ask for privileged access  Confirm  A whale icon should appear in the top bar  Click it and wait for  quot Docker is running quot  to appear  You should be able to run docker commands now  docker ps  Because docker is a system-level package  you cannot install it using brew install  and must use --cask instead  Note  This solution only works for Macs whose CPUs support virtualization  which may not include old Macs

User · Answer

I have Mac OS and I open Launchpad and select docker application  from reset tab click on restart

User · Answer

Docker for Mac is deprecated  And you don t need Homebrew to run Docker on Mac  Instead you ll likely want to install Docker Desktop or  if already installed  make sure it s up-to-date and running  then attempt to connect to the socket again

User · Answer

i simply had to run spotlight search and execute the Docker application under  Applications folder which brew cask install created  Once this was run it asked to complete installation  I was then able to run docker ps

User · Answer

I had this same issue I solved it in the following steps   docker-machine restart   Quit terminal  or iTerm2  etc  etc  and restart  eval   docker-machine env default    I also answered it here

User · Answer

I had the same problem  Docker running but couldn t access it through CLI   For me the problem was solved by executing  Docker Quickstart Terminal app   This is located in the   Applications Docker   folder  As long as I work in this instance of the Terminal app Docker works perfectly  If a second window is needed I have to run the  Quickstart  app once more   I have a Docker for Mac installation  Therefore I am not sure if my solution is valid for a Homebrew installation   The  Docker Quickstart Terminal  app seems to be essentially some applescripts to launch the terminal app and a bash start script that initialise all the necessary environment variables    Hope this helps someone else

User · Answer

This problem    brew install docker docker-machine   docker ps  Cannot connect to the Docker daemon at unix    var run docker sock  Is the docker daemon running   This apparently meant do the following    docker-machine create default   default driver is apparently vbox  Running pre-create checks    Error with pre-create check   quot VBoxManage not found  Make sure VirtualBox is installed and VBoxManage is in the path quot     brew cask install virtualbox       docker-machine create default    works this time   docker ps Cannot connect to the Docker daemon at unix    var run docker sock  Is the docker daemon running    eval  quot   docker-machine env default  quot    docker ps CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES  It finally works  You can use the    xhyve    driver if you don   t want to install virtual box  Also you can install the    docker app     then run it  which apparently makes it so you don   t have to run some of the above  brew cask install docker then run the app  see the other answers   But apparently isn t necessary per se

User · Answer

on OSX assure you have launched the Docker application before issuing  docker ps   or docker build     etc     yes it seems strange and somewhat misleading that issuing   docker --version   gives version even though the docker daemon is not running     ditto for those other version cmds      I just encountered exactly the same symptoms     this behavior on OSX is different from on linux

User · Answer

I was facing similar issue on my mac  and I found that docker wasn t running in my machine  I just went to applications and invoked whale and then it worked

User · Answer

I had docker up to date  docker said it was running  and the diagnosis was good  I needed to unset some legacy environment variable  thanks https   docs docker com docker-for-mac troubleshoot  workarounds-for-common-problems     unset DOCKER HOST unset DOCKER CERT PATH unset DOCKER TLS VERIFY

User · Answer

On macOS the docker binary is only a client and you cannot use it to run the docker daemon  because Docker daemon uses Linux-specific kernel features  therefore you can   t run Docker natively in OS X  So you have to install docker-machine in order to create VM and attach to it   Install docker-machine on macOS  If you don t have docker-machine command yet  install it by using one of the following methods    Using Brew command  brew install docker-machine docker  Manually from Releases page     curl -L https   github com docker machine releases download v0 16 1 docker-machine- uname -s - uname -m   gt  usr local bin docker-machine   chmod  x  usr local bin docker-machine    See  Get started with Docker for Mac   Install Virtualbox  docker-machine relies on VirtualBox being installed and will fail if this isn t the case  If you already have VirtualBox  you can skip this step    Using Homebrew  brew cask install virtualbox Manually using the releases on Virtualbox org   You will need to actively accept loading the Virtualbox kernel extension in the OS X Security panel and then proceed to restart the machine for the next commands not to fail with Error  VBoxNetAdpCtl  Error while adding new interface  Configure docker-machine on macOS  Create a default machine  if you don t have one  see  docker-machine ls    docker-machine create --driver virtualbox default   Then set-up the environment for the Docker client   eval    docker-machine env default     Then double-check by listing containers   docker ps   See  Get started with Docker Machine and a local VM     Related    Brew install docker does not include docker engine  For Linux  see  Docker can  39 t connect to docker daemon For Windows  see  Docker warning  failed to get default registry endpoint from daemon

User · Answer

I first tried docker and docker-compose via homebrew  but it had the problem listed here  I had to install docker s official install from https   docs docker com docker-for-mac install  and then everything worked as expected

[macos] Cannot connect to the Docker daemon on macOS

Examples related to macos

Examples related to docker

Examples related to macos-sierra