Docker Community Forums

Share and learn in the Docker community.

Docker ps fails on macOS Sierra 10.12 Beta


(Sweetaz) #1

Expected behavior

docker ps works normally

Actual behavior

Error response from daemon: Bad response from Docker engine

Information

Diagnostic ID: 27501042-A2CE-4D6D-B890-F269C3362955

Steps to reproduce the behavior

  1. … Install macOS Sierra
  2. … Install docker beta
  3. … run ‘docker ps’ in a terminal

(Sweetaz) #2

Factory reset fixes this problem.


(David Wisner) #3

I’ve had re reinstall / reset 2/3 times, and i read in another thread that docker build doesn’t work in Beta 2 (I know it works in beta 1) so I’m about to test that now. I’m pretty sure i was able to run / pull containers, now I’ll try a build


(Glynjackson) #4

Same here ‘Install macOS Sierra’ (10.12 Beta (16A238m) but a restart or complete reinstall/rebuild did not work.


(Gino Jongenelen) #5

Any results? I’m facing the exact same problem but resets did not fix it. I regret upgrading to MacOS Sierra already


(Sweetaz) #6

Current version works for me.

$ docker --version
Docker version 1.12.0-rc3, build 91e29e8, experimental
$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.12
BuildVersion:	16A239j

(Lucas Alves) #7

I’m with the same problem

➜ luk4z7 uname -a Darwin luk4z7 16.0.0 Darwin Kernel Version 16.0.0: Tue Jun 28 15:57:40 PDT 2016; root:xnu-3757.0.0.0.1~20/RELEASE_X86_64 x86_64

➜ luk4z7 docker --version Docker version 1.12.0-rc3, build 91e29e8, experimental

➜ luk4z7 sw_vers ProductName: Mac OS X ProductVersion: 10.12 BuildVersion: 16A239j


Build hangs on macOS Sierra Beta 2
(Sweetaz) #8

Don’t know what else to add. Try uninstall/reinstall, reboot, pkill -9 -f docker, ???
docker ps, docker build, docker run all working fine.


(Lucas Alves) #9

I ran the command, is now working before was instability problems, had already uninstalled and installed, but now with pkill seems to be better.

Thank you for your help.


(Lucas Alves) #10

I’m trying again, uninstalled and installed again, but when I using the containers, “docker exec”, my containers are paralesed