macOS에서 Docker 데몬에 연결할 수 없습니다

macOS에서 Docker 데몬에 연결할 수 없습니다

---

나는 일반적으로 brew로 OSX에서 내 앱을 관리하는 것을 선호합니다.

도커, 도커 작성 및 도커 기계를 설치할 수 있습니다

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

'Docker for Mac'앱을 다운로드하여 실행하지 않았습니다.

그러나 내가 달리려고 할 때

> 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'.

양말 파일을 이미 확인했습니다

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

이 제안 된 솔루션을 시도했습니다. Mac OS X sudo docker Docker 데몬에 연결할 수 없습니다. 이 호스트에서 docker 데몬이 실행되고 있습니까?

그러나이 오류 메시지가 나타납니다.

$ eval $(docker-machine env default)
Host does not exist: "default"

명령 줄 도구로 도커 서비스를 실행할 수 있습니까?

---

지원되는 Mac에서 다음을 실행하십시오.

brew cask install docker

그런 다음 Docker 앱을 시작하십시오 . 다음을 클릭하십시오. 권한있는 액세스를 요청합니다. 확인하십시오. 상단 막대에 고래 아이콘이 나타납니다. 클릭하고 "Docker is running"이 나타날 때까지 기다리십시오.

docker지금 명령 을 실행할 수 있어야합니다 .

docker ps

docker는 시스템 수준 패키지이므로를 사용하여 설치할 수 없으며 brew install대신 cask를 사용해야합니다.

참고 :이 솔루션은 CPU가 가상화를 지원하는 Mac에서만 작동하며 이전 Mac은 포함하지 않을 수 있습니다.

---

macOS에서 docker바이너리는 클라이언트 일 뿐이며 Docker 데몬은 Linux 관련 커널 기능을 사용하므로 Docker 데몬을 실행하는 데 사용할 수 없으므로 OS X에서 Docker를 기본적으로 실행할 수 없습니다. 따라서 docker-machine생성 하려면 설치해야합니다. VM에 연결하십시오.

docker-machinemacOS에 설치

docker-machine아직 명령 이 없으면 다음 방법 중 하나를 사용하여 설치하십시오.

• Brew 명령 사용 : brew install docker-machine docker.

• 릴리스 페이지 에서 수동으로 :

  $ curl -L https://github.com/docker/machine/releases/download/v0.16.1/docker-machine-`uname -s`-`uname -m` >/usr/local/bin/docker-machine
  $ chmod +x /usr/local/bin/docker-machine
  

Docker for Mac 시작하기를 참조하십시오 .

Virtualbox 설치

docker-machine설치되는 VirtualBox에 의존하며 그렇지 않은 경우 실패합니다. 이미 VirtualBox가 있으면이 단계를 건너 뛸 수 있습니다.

• Homebrew 사용하기 : brew cask install virtualbox
• Virtualbox.org 의 릴리스를 수동으로 사용

OS X 보안 패널에서 Virtualbox 커널 확장 로딩을 적극적으로 수락 한 후 다음 명령이 실패하지 않도록 시스템 을 다시 시작해야합니다.Error: VBoxNetAdpCtl: Error while adding new interface

docker-machinemacOS에서 구성

default기계를 만듭니다 (없는 경우 : 참조 docker-machine ls).

docker-machine create --driver virtualbox default

그런 다음 Docker 클라이언트의 환경을 설정하십시오.

eval "$(docker-machine env default)"

그런 다음 컨테이너를 나열하여 다시 확인하십시오.

docker ps

Docker Machine 및 로컬 VM 시작하기를 참조하십시오 .

---

관련 :

• Brew install docker does not include docker engine?
• For Linux, see: Docker can't connect to docker daemon
• For Windows, see: Docker warning: failed to get default registry endpoint from daemon

---

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

---

Try this to create default.

docker-machine create default

---

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

---

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

---

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

---

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 !

---

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 <http://gnu.org/licenses/gpl.html>

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.

---

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.

---

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

---

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 .

참고URL : https://stackoverflow.com/questions/44084846/cannot-connect-to-the-docker-daemon-on-macos