10.11.5 docker for mac failure

Expected behavior

Docker for Mac runs on fresh 10.11.5 installation.

Actual behavior

Docker for Mac hangs at ‘Getting Started’, and eventually causes the system to crash.

Information

  • the output of:
    • pinata diagnose -u on OSX
      OS X: version 10.11.5 (build: 15F34)
      Docker.app: version v1.11.1-beta13
      Running diagnostic tests:
      [ERROR] docker-cli Connection refused (ECONNREFUSED) connecting to /var/run/docker.sock: check if service is running
      [ERROR] docker-cli Connection refused (ECONNREFUSED) connecting to /Users/E/Library/Containers/com.docker.docker/Data/s60: check if service is running
      [ERROR] Moby booted /Users/E/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring does not exist
      [OK] Moby booted
      [ERROR] driver.amd64-linux Docker.app/Contents/MacOS/com.docker.driver.amd64-linux -db is not running
      [OK] driver.amd64-linux
      [OK] vmnetd
      [OK] osxfs
      [ERROR] db /Users/E/Library/Containers/com.docker.docker/Data/s40 does not exist
      [ERROR] db Unexpected error (No such file or directory) connecting to /Users/E/Library/Containers/com.docker.docker/Data/s40
      [ERROR] db com.docker.db is not running
      [OK] db
      [OK] slirp
      [OK] menubar
      [OK] environment
      [OK] Docker
      [OK] VT-x
      Docker logs are being collected into /tmp/20160527-002348.tar.gz
      Most specific failure is: com.docker.db is not running
  • 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 )
    10.11.5

Steps to reproduce the behavior

  1. Install macOS 10.11.4
  2. Update to 10.11.5
  3. Install Docker for Mac Beta 13
  4. Run Docker for Mac Beta

Might be related with this https://discussions.apple.com/thread/7576482

The update breaks the ability of mounting certain formats (such as DMG) for some users

EDIT: Thank you so much for that link, a fresh re-installlation of El Capitan managed to resolve this issue for me.

I had same problem when running Kinematic setup, but I’ve solved, starting docker before to run Kitematic Setup

It’s started happening again, after I had rebuilt my kexts on my machine, so I uploaded some diagnostics.

E4A10FC9-9BB4-46DF-96E7-A69D72A53B91