Expected behavior
I expected normal docker response.
Actual behavior
$ docker ps
Error response from daemon: dial unix /Users/Gavin/Library/Containers/com.docker.docker/Data/*00000003.00000948: connect: no such file or directory
sudo didn’t work either, it gave me the same error.
$ sudo docker ps
Error response from daemon: dial unix /Users/Gavin/Library/Containers/com.docker.docker/Data/*00000003.00000948: connect: no such file or directory
Information
- the output of:
pinata diagnose -u
on OSXDockerDebugInfo.ps1
using Powershell on Windows
- a reproducible case if this is a bug, Dockerfiles FTW
- page URL if this is a docs issue or the name of a man page
- host distribution and version ( OSX 10.10.x, OSX 10.11.x, Windows, etc )
$ pinata diagnose -u
OS X: version 10.11.5 (build: 15F34)
Docker.app: version v1.11.1-beta13
Running diagnostic tests:
[ERROR] Moby booted /Users/Gavin/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring does not exist
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160526-190146.tar.gz
Most specific failure is: /Users/Gavin/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring does not exist
Steps to reproduce the behavior
- Immediately after installing docker for Mac I tried the docker command and got the error.
- After rebooting (based on one other issue I found) the same error is showing up when I try a docker command.