# Docker ps failed **URL:** \ **Category:** Docker Desktop\ **Created:** [June 26, 2016, 10:57am UTC](https://forums.docker.com/t/docker-ps-failed/16657 "2016-06-26T10:57:17Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![roackb2](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/roackb2/32/11787_2.png) [@roackb2](https://forums.docker.com/u/roackb2)\ **Post date:** [June 26, 2016, 10:57am UTC](https://forums.docker.com/t/docker-ps-failed/16657/1 "2016-06-26T10:57:18Z")
### Expected behavior docker ps should return running containers ### Actual behavior ``` command hangs forever ``` ### Information Docker for Mac: version: mac-v1.12.0-beta16.2 OS X: version 10.11.5 (build: 15F34) logs: /tmp/20160626-185352.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 ### Steps to reproduce the behavior 1. call docker ps ---
**Author:** ![roackb2](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/roackb2/32/11787_2.png) [@roackb2](https://forums.docker.com/u/roackb2)\ **Post date:** [June 26, 2016, 11:01am UTC](https://forums.docker.com/t/docker-ps-failed/16657/2 "2016-06-26T11:01:56Z")
solved by quit docker and start it again, restart won’t work ---
**Author:** ![p3000](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/p3000/32/11841_2.png) [@p3000](https://forums.docker.com/u/p3000)\ **Post date:** [June 28, 2016, 12:27am UTC](https://forums.docker.com/t/docker-ps-failed/16657/3 "2016-06-28T00:27:15Z")
I’ve tried everything from quitting/restarting Docker to restarting the physical OS X machine, and still get this error. I can’t be the only one with this frustrating issue! Diagnostic #CF8D89D6-13F6-4C9D-9E13-F92A987450FB ---
**Author:** ![dwitherspoon](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/dwitherspoon/32/8075_2.png) [@dwitherspoon](https://forums.docker.com/u/dwitherspoon)\ **Post date:** [June 28, 2016, 3:28am UTC](https://forums.docker.com/t/docker-ps-failed/16657/4 "2016-06-28T03:28:53Z")
I ran into the same issue and I was not able to fix it by restarting either. I did remember that I had changed my preferences (memory and CPU settings) before the last update. So I decided to reset the setting back to original and after the app restarted it all worked again. Then I was able to go back into preferences and put my CPU and memory settings back. I hope that works for you. ---
**Author:** ![pcssi](https://avatars.discourse-cdn.com/v4/letter/p/71e660/32.png) [@pcssi](https://forums.docker.com/u/pcssi)\ **Post date:** [June 28, 2016, 3:41pm UTC](https://forums.docker.com/t/docker-ps-failed/16657/5 "2016-06-28T15:41:36Z")
I ran into this issue. **Diagnostic ID:** 938E9151-C826-4614-BC84-6126AC821B40 How I resolved it was by deleting the $HOME/Library/Containers/com.docker.docker/Data/ directory which is not an ideal workaround as it blew away all my local images. I looked through the `docker-system.log` in `/tmp/.tar.gz` . > > > … > > > Docker[com.docker.slirp][2830] : attempting to reconnect to database on unix $HOME/Library/Containers/com.docker.docker/Data/s40 > > > … In retrospect, I would have started by taking a more limited approach to removing directories; maybe starting with `$HOME/Library/Containers/com.docker.docker/Data/s40`. Hope this helps those with this issue. [edit] resolved the issue. ---
**Author:** ![p3000](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/p3000/32/11841_2.png) [@p3000](https://forums.docker.com/u/p3000)\ **Post date:** [June 28, 2016, 4:26pm UTC](https://forums.docker.com/t/docker-ps-failed/16657/6 "2016-06-28T16:26:49Z")
@dwitherspoon / @pcssi, Thanks for the suggestions! Changing the CPU/RAM settings didn’t work. Eventually, I had to use the “Factory Reset” feature, which seems to effectively start from scratch. This was highly undesirable since I lost all my local images and containers, but at least i’m rolling again. 😕 For anyone in the same boat after an upgrade, if it’s not too burdensome to restore or recreate your images, I wouldn’t waste a lot of time trying to manually troubleshoot. The factory reset is crude, but effective. ---
**Author:** ![pcssi](https://avatars.discourse-cdn.com/v4/letter/p/71e660/32.png) [@pcssi](https://forums.docker.com/u/pcssi)\ **Post date:** [June 28, 2016, 4:40pm UTC](https://forums.docker.com/t/docker-ps-failed/16657/7 "2016-06-28T16:40:37Z")
@p3000, great suggestion. This is essentially what I did from the command line. I was not aware the application exposed this. For those who are unaware, if you click on the Docker icon in the menu bar and navigate to _Preferences…_ ( keyboard shortcut `⌘,` ); the following window will show up. ![](https://global.discourse-cdn.com/docker/original/2X/4/42b0927480cee8aede7080da6f7110a548464007.png) The General, Advanced, or Uninstall / Reset “tab” will be selected depending on the state of your application. ---
**Author:** ![jzila](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/jzila/32/11882_2.png) [@jzila](https://forums.docker.com/u/jzila)\ **Post date:** [June 28, 2016, 6:57pm UTC](https://forums.docker.com/t/docker-ps-failed/16657/8 "2016-06-28T18:57:12Z")
Also broken here, diagnostic ID F92CC360-9C07-4D1A-9A70-FEF8218EEECE. Restarting docker does nothing, and rebooting the PC does nothing. The Docker tray widget hangs on `Docker starting...`