{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/16819","labels_url":"https://api.github.com/repos/docker/docker/issues/16819/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/16819/comments","events_url":"https://api.github.com/repos/docker/docker/issues/16819/events","html_url":"https://github.com/docker/docker/issues/16819","id":110271281,"number":16819,"title":"docker commands hang on Ubuntu (vivid) today","user":{"login":"mbruzek","id":6385185,"avatar_url":"https://avatars.githubusercontent.com/u/6385185?v=3","gravatar_id":"","url":"https://api.github.com/users/mbruzek","html_url":"https://github.com/mbruzek","followers_url":"https://api.github.com/users/mbruzek/followers","following_url":"https://api.github.com/users/mbruzek/following{/other_user}","gists_url":"https://api.github.com/users/mbruzek/gists{/gist_id}","starred_url":"https://api.github.com/users/mbruzek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mbruzek/subscriptions","organizations_url":"https://api.github.com/users/mbruzek/orgs","repos_url":"https://api.github.com/users/mbruzek/repos","events_url":"https://api.github.com/users/mbruzek/events{/privacy}","received_events_url":"https://api.github.com/users/mbruzek/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-10-07T17:00:13Z","updated_at":"2015-11-09T18:06:54Z","closed_at":null,"body":"# Description of problem: docker commands hang on Ubuntu\r\n\r\n`docker version`: Version:      1.9.0-dev  Git commit:   1529343\r\n\r\n`docker info`: not available (command hangs)\r\n\r\n`uname -a`: Linux warhorse 3.19.0-30-generic #34-Ubuntu SMP Fri Oct 2 22:08:41 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux  \r\n\r\n### Environment details (AWS, VirtualBox, physical, etc.):  \r\nPhysical Ubuntu Vivid (15.04) system.  \r\n\r\n### How reproduce:  \r\nI am using the docker experimental build on Ubuntu Vivid (15.04).  Today I am not able to complete any docker commands they all hang indefinitely.   \r\n\r\n### Steps to Reproduce:\r\n1. `sudo docker -D info`        (hangs)\r\n2. `sudo docker version`       (hangs) \r\n3. `sudo systemctl restart docker`  \r\nJob for docker.service failed. See \"systemctl status docker.service\" and \"journalctl -xe\" for details.\r\n\r\n### Actual Results:  \r\nAll the docker client commands hang.  The docker daemon issues an error but *is* running.  \r\n\r\n### Expected Results:  \r\nThe docker commands should work even if they can not contact the daemon.\r\n\r\n### Additional info:\r\n\r\nThis morning I am unable to run any docker commands successfully.  I suspected the docker daemon might have problems so I restarted that service and got a message that it failed:\r\n\r\n$ sudo systemctl restart docker\r\nJob for docker.service failed. See \"systemctl status docker.service\" and \"journalctl -xe\" for details.\r\n\r\nEverything appears to be running checking docker.service and ps shows the docker daemon running.\r\n\r\n$ `sudo systemctl status docker.service -l`\r\n● docker.service - Docker Application Container Engine\r\n   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)\r\n   Active: failed (Result: exit-code) since Wed 2015-10-07 13:39:25 CDT; 16s ago\r\n     Docs: https://docs.docker.com\r\n  Process: 25371 ExecStart=/usr/bin/docker daemon -H fd:// (code=exited, status=2)\r\n Main PID: 25371 (code=exited, status=2)\r\n\r\nOct 07 13:37:55 warhorse systemd[1]: Starting Docker Application Container Engine...\r\nOct 07 13:37:55 warhorse docker[25371]: time=\"2015-10-07T13:37:55-05:00\" level=warning msg=\"Running experimental build\"\r\nOct 07 13:39:25 warhorse systemd[1]: docker.service start operation timed out. Terminating.\r\nOct 07 13:39:25 warhorse systemd[1]: docker.service: main process exited, code=exited, status=2/INVALIDARGUMENT\r\nOct 07 13:39:25 warhorse systemd[1]: Failed to start Docker Application Container Engine.\r\nOct 07 13:39:25 warhorse systemd[1]: Unit docker.service entered failed state.\r\nOct 07 13:39:25 warhorse systemd[1]: docker.service failed.\r\n\r\n\r\nAccording to syslog the last start of the Docker Application Engine failed.\r\n/var/log/syslog:  \r\n...  \r\nOct  7 13:37:55 warhorse systemd[1]: docker.service: main process exited, code=exited, status=2/INVALIDARGUMENT\r\nOct  7 13:37:55 warhorse systemd[1]: Unit docker.service entered failed state.\r\nOct  7 13:37:55 warhorse systemd[1]: docker.service failed.\r\nOct  7 13:37:55 warhorse systemd[1]: Stopping Docker Socket for the API. \r\nOct  7 13:37:55 warhorse systemd[1]: Starting Docker Socket for the API. \r\nOct  7 13:37:55 warhorse systemd[1]: Listening on Docker Socket for the API. \r\nOct  7 13:37:55 warhorse systemd[1]: Starting Docker Application Container Engine...\r\nOct  7 13:37:55 warhorse docker[25371]: time=\"2015-10-07T13:37:55-05:00\" level=warning msg=\"Running experimental build\"\r\nOct  7 13:39:25 warhorse systemd[1]: docker.service start operation timed out. Terminating.\r\nOct  7 13:39:25 warhorse systemd[1]: docker.service: main process exited, code=exited, status=2/INVALIDARGUMENT\r\nOct  7 13:39:25 warhorse systemd[1]: Failed to start Docker Application Container Engine.\r\nOct  7 13:39:25 warhorse systemd[1]: Unit docker.service entered failed state.\r\nOct  7 13:39:25 warhorse systemd[1]: docker.service failed.\r\n\r\nAll docker commands hang for me.  Is there any other file or information you need to diagnose this problem?  Are there any workarounds at this time?\r\n"},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/155142500","html_url":"https://github.com/docker/docker/issues/16819#issuecomment-155142500","issue_url":"https://api.github.com/repos/docker/docker/issues/16819","id":155142500,"user":{"login":"mbruzek","id":6385185,"avatar_url":"https://avatars.githubusercontent.com/u/6385185?v=3","gravatar_id":"","url":"https://api.github.com/users/mbruzek","html_url":"https://github.com/mbruzek","followers_url":"https://api.github.com/users/mbruzek/followers","following_url":"https://api.github.com/users/mbruzek/following{/other_user}","gists_url":"https://api.github.com/users/mbruzek/gists{/gist_id}","starred_url":"https://api.github.com/users/mbruzek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mbruzek/subscriptions","organizations_url":"https://api.github.com/users/mbruzek/orgs","repos_url":"https://api.github.com/users/mbruzek/repos","events_url":"https://api.github.com/users/mbruzek/events{/privacy}","received_events_url":"https://api.github.com/users/mbruzek/received_events","type":"User","site_admin":false},"created_at":"2015-11-09T18:06:54Z","updated_at":"2015-11-09T18:06:54Z","body":"@jaredbroad - The docker update (delivered via apt-get upgrade) on October 14th 2015 fixed my issue.  I suspect that the version of docker for 16.04 was lagging behind the other releases of the same package and it just caught up in the next update.\r\n\r\nI the problem it had everything to do with an invalid argument, I had considered editing the systemd start up file, but the update fixed me before I dug into that.  The key was to figure out the argument that is invalid and either comment it out, or call it's no deprecated version.\r\n\r\nIt is still running for me, please let me know if you need any specific information from my machine to compare against your machine."}}