Docker Community Forums

Share and learn in the Docker community.

Docker 1.11.2-Beta15 wont start at all

build
beta
docker

(Techgourmet) #1

Expected behavior

Docker starts

Actual behavior

Docker does not start

Information

  • the output of:
    • pinata diagnose -u on OSX (Pinata not found)

Diagnostic ID: A3A68A1C-4B5F-8B6C-F447BAEC4F7E

  • a reproducible case if this is a bug, Dockerfiles FTW (Not applicable)

  • host distribution and version (OSX 10.11.5)

Steps to reproduce the behavior

  1. start docker

(Itamar Ostricher) #2

I’m seeing the same behavior. Here’s my diagnostic output:

Docker for Mac: version: mac-v1.11.2-beta15
OS X: version 10.11.5 (build: 15F34)
logs: /tmp/20160614-094924.tar.gz
failure: docker ps failed: Failure("docker ps: timeout after 10.00s")
[ERROR]  docker-cli
         docker ps failed
[OK]     app
[OK]     menubar
[OK]     virtualization
[OK]     system
[OK]     osxfs
[OK]     db
[OK]     slirp
[OK]     moby-console
[OK]     logs
[OK]     vmnetd
[OK]     env
[OK]     moby
[OK]     driver.amd64-linux

Diagnostic ID: 2C592E17-3461-47C5-A369-56E2B67A5E4E

Started immediately after the upgrade to beta 1.11.2-beta15. Persists after system reboot.


(Misterdelle) #3

Also for me on Windows 10 Pro Build: 10586


(Marcin Ryżycki) #4

Same here. Diagnostic ID: B6B57083-1893-494D-80BB-1826D51401FD

Docker for Mac: version: mac-v1.11.2-beta15
OS X: version 10.11.6 (build: 15G12a)
logs: /tmp/20160614-123931.tar.gz
failure: docker ps failed: Failure("docker ps: timeout after 10.00s")
[ERROR]  docker-cli
         docker ps failed
[OK]     app
[OK]     menubar
[OK]     virtualization
[OK]     system
[OK]     osxfs
[OK]     db
[OK]     slirp
[OK]     moby-console
[OK]     logs
[OK]     vmnetd
[OK]     env
[OK]     moby
[OK]     driver.amd64-linux

(Marcin Ryżycki) #5

Surprisingly, it worked for a day or so when I installed the beta15 update, at least for a couple of hours.

It must have exited some time afterwards, today morning I have the issue as described in the 1st post (docker is starting infinitely).

Temporary workaround which worked for me: Preferences -> Uninstall/Reset tag -> Reset to factory defaults. Now it starts, even after exiting/restarting the Docker app.


(Astrohome) #6

The same for me! Diag id: BD6ADB43-5362-4EA7-B044-23A9FB1992E0


(Tony Pujals) #7

I can confirm that Preferences -> Reset was all I had to do to get this working again. It required resubmitting my invitation code. Migrating my Default machine did not work, however.


(Lev4ik) #8

Same here, diagnose id : 1A2BAAB0-A0CE-4B10-9E8D-8198EC6BAD4B