# Bad response from Docker engine after upgrading **URL:** \ **Category:** Docker Desktop\ **Created:** [July 5, 2016, 8:53pm UTC](https://forums.docker.com/t/bad-response-from-docker-engine-after-upgrading/17458 "2016-07-05T20:53:35Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![pwnall](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/pwnall/32/10265_2.png) [@pwnall](https://forums.docker.com/u/pwnall)\ **Post date:** [July 5, 2016, 8:53pm UTC](https://forums.docker.com/t/bad-response-from-docker-engine-after-upgrading/17458/1 "2016-07-05T20:53:35Z")
### Expected behavior For the past few Docker for Mac upgrades, applying an upgrade should not break my installation. ### Actual behavior After an upgrade, I get `Error response from daemon: Bad response from Docker engine` in response to `docker` commands. Restarting Docker doesn’t help. I have to use factory reset to get back to a working state. ### Information - the output of: - host distribution and version ( OSX 10.10.x, OSX 10.11.x, Windows, etc ) OSX 10.11.6 Beta (15G24b) FWIW, this isn’t a deal breaker for me. Mostly filing the issue in case the diagnostic info helps uncover a more serious bug. ### Steps to reproduce the behavior 1. Wait for a Docker for Mac upgrade. (might be able to repro this by downloading and installing an old Docker for Mac?) 2. Try doing a `docker ps` ---
**Author:** ![pwnall](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/pwnall/32/10265_2.png) [@pwnall](https://forums.docker.com/u/pwnall)\ **Post date:** [July 8, 2016, 10:04pm UTC](https://forums.docker.com/t/bad-response-from-docker-engine-after-upgrading/17458/2 "2016-07-08T22:04:31Z")
After a bunch of upgrades, this happens after every reboot. Diagnostic ID: 849F10C4-6CB7-4DA4-8B1B-ABBE9317A2FF Docker for Mac: version: mac-v1.12.0-beta18-3-gec40b14 OS X: version 10.11.6 (build: 15G26a) ---
**Author:** ![pwnall](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/pwnall/32/10265_2.png) [@pwnall](https://forums.docker.com/u/pwnall)\ **Post date:** [July 16, 2016, 8:33pm UTC](https://forums.docker.com/t/bad-response-from-docker-engine-after-upgrading/17458/3 "2016-07-16T20:33:07Z")
Still happening with the next beta. Diagnostic ID: 24385DFF-477B-4CF6-B732-638985B815F8 Docker for Mac: version: win-v1.12.0-beta19 OS X: version 10.11.6 (build: 15G26a) ---
**Author:** ![yichen](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/yichen/32/12869_2.png) [@yichen](https://forums.docker.com/u/yichen)\ **Post date:** [August 4, 2016, 11:51pm UTC](https://forums.docker.com/t/bad-response-from-docker-engine-after-upgrading/17458/4 "2016-08-04T23:51:52Z")
I am having the same issue, getting this error message after machine reboot. This is my docker for mac version: Version 1.12.0 (build: 10871) ---
**Author:** ![brandonaaskov](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/brandonaaskov/32/12884_2.png) [@brandonaaskov](https://forums.docker.com/u/brandonaaskov)\ **Post date:** [August 5, 2016, 2:48pm UTC](https://forums.docker.com/t/bad-response-from-docker-engine-after-upgrading/17458/5 "2016-08-05T14:48:27Z")
Same here, getting this message after an upgrade. Also running Version 1.12.0 (build: 10871). I solved this by going to Docker Preferences \> Uninstall/Reset \> Reset Factory Settings. That got the engine running again, and after it rebooted, the toolbox migration assistant moved my images over. Back up and running! ---
**Author:** ![asung](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@asung](https://forums.docker.com/u/asung)\ **Post date:** [August 20, 2016, 7:58am UTC](https://forums.docker.com/t/bad-response-from-docker-engine-after-upgrading/17458/6 "2016-08-20T07:58:34Z")
Thanks. I had the same issue but I was able to solve it following your instruction.