Docker Community Forums

Share and learn in the Docker community.

Docker host not running after VBox upgrade to 5.0.20


(David Gethings) #1

Expected behaviour

That the docker host will be up

Actual behaviour

In Docker Settings -> Advanced Docker host is reported as running
’docker version’ is unable to connect to the docker host
VBox Manager reporting the ‘default’ VM as Powered Off
Applying advanced setting does not appear to restart the docker host - even though the UI reports a successful restart

Information

$ pinata diagnose -u
OS X: version 10.11.5 (build: 15F34)
Docker.app: version v1.11.1-beta12
Running diagnostic tests:
[ERROR] docker-cli /var/run/docker.sock does not exist
[ERROR] docker-cli Unexpected error (No such file or directory) connecting to /var/run/docker.sock
[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/20160524-162133.tar.gz
Most specific failure is: Unexpected error (No such file or directory) connecting to /var/run/docker.sock
Your unique id is: B87A375B-3230-48D1-B600-3C619327980C
Please quote this in all correspondence.

Following output produced after manually starting the docker host via VBox Manager:
$ pinata diagnose -u
OS X: version 10.11.5 (build: 15F34)
Docker.app: version v1.11.1-beta12
Running diagnostic tests:
[ERROR] docker-cli /var/run/docker.sock does not exist
[ERROR] docker-cli Unexpected error (No such file or directory) connecting to /var/run/docker.sock
[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/20160524-162340.tar.gz
Most specific failure is: Unexpected error (No such file or directory) connecting to /var/run/docker.sock
Your unique id is: B87A375B-3230-48D1-B600-3C619327980C
Please quote this in all correspondence.

Steps to reproduce the behavior

  1. …Upgrade VBox Manager to 5.0.20
  2. …reboot OS X

(David Gethings) #2

Just to confirm. This problem is now fixed after a Docker reset.