Docker Community Forums

Share and learn in the Docker community.

Docker-cli not working after update to Version 1.11.1-beta10


(Mike Chernev) #1

Expected behavior

Run Docker commands from the CLI

Actual behavior

Getting docker: Error response from daemon: Bad response from Docker engine.

Information

pinata diagnose -u

OS X: version 10.10.3 (build: 14D131)
Docker.app: version v1.11.1-beta10
Running diagnostic tests:
Error docker ps: timeout after 10.00s
[ERROR]   docker-cli       docker ps failed: Misc.Failure
[OK]      docker-cli
[OK]      Moby booted
[OK]      driver.amd64-linux
[OK]      vmnetd
[OK]      osxfs
[OK]      db
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Error docker ps: got timeout (docker ps: exit 1)
Thread 6 killed on uncaught exception Misc.Failure
  • host distribution and version OSX 10.10.3

Steps to reproduce the behavior

  1. Update the Docker for Mac app

(Tobias Gesellchen) #2

@mikechernev the upgrade worked for me on Mac. It seems like you’re working on Windows?!


(Mike Chernev) #3

I am working on Yosemite (MacOS 10.10.3). The Windows bit was from the boilerplate for a post, it is updated now.
If it works for you, I will try to reinstall the Docker app and see if this will fix it.


(Mike Chernev) #4

Reseting to factory defaults fixed it.


(Maksim Ramanouski) #5

+1 on that.

pinata diagnose -u 19:00:23 [:arrow_forward::arrow_forward::arrow_forward::arrow_forward::arrow_forward::arrow_forward::arrow_forward::arrow_forward::arrow_forward::arrow_forward:]
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.1-beta10
Running diagnostic tests:
Error docker ps: timeout after 10.00s
[ERROR] docker-cli docker ps failed: Misc.Failure
[OK] docker-cli
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Error docker ps: got timeout (docker ps: exit 1)
Thread 6 killed on uncaught exception Misc.Failure
Docker logs are being collected into /tmp/20160504-190024.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Your unique id is: BB085163-2363-41FB-BB3B-627E255C1E74
Please quote this in all correspondence.


(Vincentcr) #6

having the same issue:


OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.1-beta10
Running diagnostic tests:
Error docker ps: timeout after 10.00s
[ERROR]   docker-cli       docker ps failed: Misc.Failure
[OK]      docker-cli
[OK]      Moby booted
[OK]      driver.amd64-linux
[OK]      vmnetd
[OK]      osxfs
[OK]      db
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Error docker ps: got timeout (docker ps: exit 1)
Thread 6 killed on uncaught exception Misc.Failure
Docker logs are being collected into /tmp/20160505-210711.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Your unique id is: 0292B76B-BB5E-4698-89DE-007514884509
Please quote this in all correspondence.

(Mike Chernev) #7

@vincentcr @maxromanovsky
As I mentioned earlier - reseting the docker app to factory defaults fixed this for me. You should bear in mind that any local images will be lost, so make sure you commit and push those if you want to preserve them :slight_smile:
Hope this works for you too.

Cheers,
Mike


Docker not starting on OS X
(Simonturvey) #8

Worked for me too. I guess there’s some cruft left behind from previous kitematic experiments or similar.


(Vincentcr) #9

yeah, it worked for me too, although i wouldn’t call a full reset “fixing it” :slight_smile:


(Ronicthomas) #10

worked for me as well after resetting! more of a “hack” than a fix though!


(Sean Timm) #11

I’m setting up a new Mac with a fresh OS. This was the first and only version of Docker I’ve installed (no Kitematic, etc), and I had the same problem (which the full reset fixed).


(Chmihai) #12

Some problem but with beta11
Reseting the docker does not fix the issue.

OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.1-beta11
Running diagnostic tests:
Error docker ps: timeout after 10.00s
[ERROR] docker-cli docker ps failed: Misc.Failure
[OK] docker-cli
[OK] Moby booted
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
[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/20160510-231042.tar.gz

Any suggestions ?


(Chmihai) #13

got it running by uninstalling, disabling Kaspersky and install again!


(Mike Chernev) #14

I had something similar for beta 11, but I only had to restart the app. Without any resets or reinstalls.


(Xer0x) #15

Thanks for sharing this. I had to click “Factory Reset” to fix it also.


(Matt Brender) #16

Ran into similar as of Version 1.11.1-beta12. Whale icon showing Green and Running, but docker ps hangs.

$ pinata diagnose -u
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.1-beta12
Running diagnostic tests:
[OK]      Moby booted
[OK]      driver.amd64-linux
[OK]      vmnetd
[OK]      osxfs
[OK]      db
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Error exec: echo "00000003.0000f3a6" | nc -U /Users/mjbrende/Library/Containers/com.docker.docker/Data/@connect > /tmp/20160518-122501/diagnostics.tar: exit 1
Docker logs are being collected into /tmp/20160518-122501.tar.gz
Most specific failure is: No error was detected
Error exec: /usr/bin/curl -L -X PUT -T '/tmp/20160518-122501.tar.gz' -H 'Host: docker-pinata-support' -H 'Date: Wed, 18 May 2016 12:25:05 PDT' -H 'x-amz-acl: bucket-owner-full-control' -H 'Content-type: application/json' https://docker-pinata-support.s3.amazonaws.com/incoming/2/D02CC2E0-3C9E-400D-923E-24AC8E75972A/20160518-122501/report.tar: exit 35
diagnose: internal error, uncaught exception:
          Misc.Failure

Did a factory reset and it’s back to good. Just want to share stats to help :thumbsup:


(Ngu04) #17

I have hang issue with docker for mac and reset has fixed it :slight_smile: . Thanks guys for this post !


(Dcmwong) #18

Hi,

Can someone describe what they mean by “factory reset”.

my docker-cli fails once every so often but it’s happening more regularly with Version 1.12.0-rc2-beta16 (build: 9493)

I find if I do

docker-machine restart
eval $(docker-machine env)

it works again but this is inconvenient.


(Alexandre) #19

@dcmwong,

If you have using Docker for Mac, you shouldn’t be using docker-machine and you shouldn’t have any DOCKER* environment variables (do env | grep -i DOCKER in a terminal and make sure there’s nothing there)

Docker for Mac is resetted using the Preferences tab (accessible from the Docker icon in the Mac toolbar):