无法开始与docker工作
我使用Ubuntu 16.04。
突然（对不起），我不能运行docker。 当我在terminal运行命令时，我只有这个（预期的输出是有关客户端和守护进程版本的信息）：
$ sudo docker --version Docker version 1.12.3, build 6b644ec 当我运行命令行这一点
$ sudo docker ps
我什么也没有很久
我怎样才能克服这个问题？
$ sudo service docker status ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Ср 2017-01-04 18:14:48 MSK; 12s ago Docs: https://docs.docker.com Process: 9534 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE) Main PID: 9534 (code=exited, status=1/FAILURE) янв 04 18:14:47 kenenbek dockerd[9534]: time="2017-01-04T18:14:47.446210980+03:00" level=warning msg="Your kernel does not support swap memory limit." янв 04 18:14:47 kenenbek dockerd[9534]: time="2017-01-04T18:14:47.447160673+03:00" level=info msg="Loading containers: start." янв 04 18:14:47 kenenbek dockerd[9534]: .................time="2017-01-04T18:14:47.469385119+03:00" level=info msg="Firewalld running: false" янв 04 18:14:47 kenenbek dockerd[9534]: time="2017-01-04T18:14:47.881263583+03:00" level=info msg="Default bridge (docker0) is assigned with an IP addr янв 04 18:14:48 kenenbek dockerd[9534]: time="2017-01-04T18:14:48.736641043+03:00" level=info msg="Loading containers: done." янв 04 18:14:48 kenenbek dockerd[9534]: time="2017-01-04T18:14:48.790061315+03:00" level=fatal msg="Error creating cluster component: error while loadi янв 04 18:14:48 kenenbek systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE янв 04 18:14:48 kenenbek systemd[1]: Failed to start Docker Application Container Engine. янв 04 18:14:48 kenenbek systemd[1]: docker.service: Unit entered failed state. янв 04 18:14:48 kenenbek systemd[1]: docker.service: Failed with result 'exit-code'.
当我运行时，当我得到这样的输出：
$ sudo service docker restart Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
这看起来像这里报告的docker群证书相关的问题
此问题的解决scheme将在版本1.13发布。 现在，您可以尝试强制重新创build群体，如此处所述。