Docker Community Forums

Share and learn in the Docker community.

Installed over docker-machine for Mac unable to start beta docker daemon


(Aleclaza) #1

Expected behavior

In a fresh terminal docker ps and docker version should find the daemon

Actual behavior

docker ps and docker version hang

Information

I had docker-machine on before and it said it found my containers and copied them but a fresh shell “docker version” hung up. I started up docker-machine thinking maybe that was upgrade to us xhyve but it started the VM in virtualbox just like before and when I stopped the default VM docker wasn’t responding again so it was just using the old setup.

OS X: version 10.11.5 (build: 15F34)
Docker.app: version: v1.11.1-beta14.5.m
Running diagnostic tests:
Error docker ps: timeout after 10.00s
Error docker ps: timeout after 10.00s
[ERROR] docker-cli docker ps failed: Failure(“docker ps: timeout after 10.00s”)
[OK] docker-cli
[ERROR] Moby booted /Users/alec/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
[ERROR] osxfs com.docker.osxfs is not running
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Error exec: echo “00000003.0000f3a6” | nc -U /Users/alec/Library/Containers/com.docker.docker/Data/@connect > /tmp/20160609-162839/diagnostics.tar: exit 1
Docker logs are being collected into /tmp/20160609-162839.tar.gz
Most specific failure is: com.docker.osxfs is not running
Your unique id is: 46C59EBF-F2A5-4208-BD5A-3C05B5CA96D7

Steps to reproduce the behavior

  1. Have docker-machine and a pair of VM’s in virtualbox to start
  2. Installed Docker for Mac beta
  3. Daemon doesn’t work

(Rohinton Kazak) #2

The Docker toolbox and Docker App are two distinct entities. I would first
check to ensure that there is no setup of the former being done. Then retry
the App.
If you don’t need the docker toolbox install then maybe remove it and
reinstall the App.


(Aleclaza) #3

I can try that but it sort of defeats the purpose of the copy functionality…


(Aleclaza) #4

After another reboot the docker daemon started properly. Odd but glad it’s OK.