啟動docker報錯的解決方法：1、開啟docker並新增內容為「OPTIONS="--selinux-enabled..."」；2、將iptables的filter表清空；3、執行「docker -storage-setup」指令等等。
本文操作環境：CentOS 7.2系統、Docker 18.04.0版、Dell G3電腦。
啟動docker報錯如何解決？
Docker啟動時的報錯總結
八個Docker常見故障
錯誤一：error initializing graphdriver
Docker啟動錯誤
#系統是CentOS 7.2
系統核心及docker版本如下：
[root@docker ~]# uname -r
3.10.0-327.el7.x86_64
[root@docker ~]#
[root@docker ~]#
[root@docker ~]#
[root@docker ~]# docker version
Client:
Version: 18.04.0-ce
API version: 1.37
Go version: go1.9.4
Git commit: 3d479c0
Built: Tue Apr 10 18:21:36 2018
OS/Arch: linux/amd64
Experimental: false
Orchestrator: swarm
Server:
Engine:
Version: 18.04.0-ce
API version: 1.37 (minimum version 1.12)
Go version: go1.9.4
Git commit: 3d479c0
Built: Tue Apr 10 18:25:25 2018
OS/Arch: linux/amd64
Experimental: false
登入後複製
啟動錯誤提示如下：
[root@docker ~]# systemctl start docker
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journ
[root@docker ~]#
[root@docker ~]#
[root@docker ~]#
[root@docker ~]# systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)
Active: failed (Result: start-limit) since 日 2018-04-22 20:52:39 CST; 5s ago
Docs: https://docs.docker.com
Process: 4810 ExecStart=/usr/bin/dockerd (code=exited, status=1/FAILURE)
Main PID: 4810 (code=exited, status=1/FAILURE)
4月 22 20:52:39 docker.cgy.com systemd[1]: Failed to start Docker Application Container Engine.
4月 22 20:52:39 docker.cgy.com systemd[1]: Unit docker.service entered failed state.
4月 22 20:52:39 docker.cgy.com systemd[1]: docker.service failed.
4月 22 20:52:39 docker.cgy.com systemd[1]: docker.service holdoff time over, scheduling restart.
4月 22 20:52:39 docker.cgy.com systemd[1]: start request repeated too quickly for docker.service
4月 22 20:52:39 docker.cgy.com systemd[1]: Failed to start Docker Application Container Engine.
4月 22 20:52:39 docker.cgy.com systemd[1]: Unit docker.service entered failed state.
4月 22 20:52:39 docker.cgy.com systemd[1]: docker.service failed.
登入後複製
從以上報錯提示訊息中也沒看到錯誤的具體原因。然後我又用dockerd來直接啟動，就在輸出訊息最下面看到一條錯誤提示，如下：
[root@docker ~]# dockerd
INFO[2018-04-22T21:12:46.111704443+08:00] libcontainerd: started new docker-containerd process pid=5903
INFO[0000] starting containerd module=containerd revision=773c489c9c1b21a6d78b5c538cd395416ec50f88 version=v1.0.3
。。。。。。省略一部分输出。。。。。。
INFO[0000] loading plugin "io.containerd.grpc.v1.introspection"... module=containerd type=io.containerd.grpc.v1
INFO[0000] serving... address="/var/run/docker/containerd/docker-containerd-debug.sock" module="containerd/debug"
INFO[0000] serving... address="/var/run/docker/containerd/docker-containerd.sock" module="containerd/grpc"
INFO[0000] containerd successfully booted in 0.002763s module=containerd
Error starting daemon: error initializing graphdriver: overlay: the backing xfs filesystem is formatted without d_type support, which leads to incorrect behavior. Reformat the filesystem with ftype=1 to en d_type support. Backing filesystems without d_type support are not supported.
登入後複製
根據最後的報錯Error starting daemon: 搜尋到這篇博客，得到解決。
https://blog.csdn.net/liu9718214/article/details/79134900
具體解決方法是：
vim /etc/sysconfig/docker
加入如下：
OPTIONS="--selinux-enabled --log-driver=journald --signature-verification=false"
登入後複製
/etc/docker/daemon.json
加入以下內容：
{
"registry-mirrors": ["http://4a1df5ef.m.daocloud.io"], # 是用来pull容器加速用的，跟此次问题无关。
"storage-driver": "devicemapper" # 解决此次问题
}登入後複製
然後重啟docker，順利解決：
[root@docker ~]# systemctl restart docker
[root@docker ~]#
[root@docker ~]#
[root@docker ~]# ps aux | grep docker
root 5922 1.7 1.6 528432 62568 ? Ssl 21:15 0:00 /usr/bin/dockerd
root 5927 1.1 0.5 356984 22100 ? Ssl 21:15 0:00 docker-containerd --config /var/run/docker/containerd/containerd.toml
root 6028 0.0 0.0 112664 964 pts/0 S+ 21:15 0:00 grep --color=auto docker
登入後複製
報錯二：iptables failed
FirewallD
CentOS-7 中介紹了firewalld，firewall的底層是使用iptables進行資料過濾，建立在iptables之上，這可能會與Docker 產生衝突。
當 firewalld 啟動或重新啟動的時候，將會從 iptables 中移除 DOCKER 的規則，從而影響了 Docker 的正常運作。
當你使用的是 Systemd 的時候， firewalld 會在 Docker 之前啟動，但是如果你在 Docker 啟動之後再啟動 或重新啟動 firewalld ，你就需要重新啟動 Docker 進程了。
系統：
[root@controller ~]# cat /etc/redhat-release
CentOS Linux release 7.0.1406 (Core)
登入後複製
報錯提示如下：
[root@controller ~]# docker run -it -P docker.io/nginx
/usr/bin/docker-current: Error response from daemon: driver failed programming external connectivity on endpoint gloomy_kirch (10289e7a87e65771da90cda531951b7339bee9cb5953474460451cd48013aff0): iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 32810 -j DNAT --to-destination 172.17.0.2:80 ! -i docker0: iptables: No chain/target/match by that name.
(exit status 1).
登入後複製
這是由於在運行這次容器之前，成功啟動過一次，在上次訪問時，因為防火牆的問題導致無法正常存取Nginx，所以將iptables的filter表清空了，並且重啟過iptables，然後再次運行時，就報了以上錯誤。
解決方法
重啟防火牆
#CentOS 7下执行
[root@controller ~]# systemctl restart firewalld
登入後複製
再重啟docker守護程式即可
[root@controller ~]# systemctl restart docker
登入後複製
再次在容器中執行一個nginx就不會報錯了
[root@controller ~]# docker run -it --name nginx -p 80:80 -v /www:/wwwroot docker.io/nginx /bin/bash
root@a8a92c8f7760:/#
登入後複製
報錯三: Unable to take ownership of thin-pool
docker daemon啟動失敗：Unable to take ownership of thin-pool
Apr 27 13:51:59 master systemd: Started Docker Storage Setup.
Apr 27 13:51:59 master systemd: Starting Docker Application Container Engine...
Apr 27 13:51:59 master dockerd-current: time="2018-04-27T13:51:59.088441356+08:00" level=warning msg="could not change group /var/run/docker.sock to docker: group docker not found"
Apr 27 13:51:59 master dockerd-current: time="2018-04-27T13:51:59.091166189+08:00" level=info msg="libcontainerd: new containerd process, pid: 20930"
Apr 27 13:52:00 master dockerd-current: Error starting daemon: error initializing graphdriver: devmapper: Unable to take ownership of thin-pool (docker--vg-docker--pool) that already has used data blocks
Apr 27 13:52:00 master systemd: docker.service: main process exited, code=exited, status=1/FAILURE
Apr 27 13:52:00 master systemd: Failed to start Docker Application Container Engine.
Apr 27 13:52:00 master systemd: Unit docker.service entered failed state.
Apr 27 13:52:00 master systemd: docker.service failed
登入後複製
原因： /var/lib/ docker/devicemapper/metadata/ 內metadata遺失
workaround：
https://bugzilla.redhat.com/show_bug.cgi?id=1321640#c5
Eric Paris 2016-04-27 08:20:10 EDT
I feel like the kcs kinda misses telling users the actual problem. Nor does it really make it clear the solution.
IF you are using device mapper (instead of loopback) /var/lib/docker contains metadata informing docker about the contents of the device mapper storage area. If you delete /var/lib/docker that metadata is lost. Docker is then able to detect that the thin pool has data but docker is unable to make use of that information. The only solution is to delete the thin pool and recreate it so that both the thin pool and the metadata in /var/lib/docker will be empty.
登入後複製
解決方法：
執行指令：rm -rf /var/lib/docker/*
執行指令：rm -rf /etc/sysconfig/docker-storage
執行指令： lvremove /dev/docker-vg/docker-pool
#使用現有的docker-vg LVM磁碟區組：
#
cat <<EOF > /etc/sysconfig/docker-storage-setup
VG=docker-vg
EOF
登入後複製
# 報錯四： write /sys/fs/cgroup/cpuset/docker/cpuset.cpus: invalid argument
docker run運行容器時報如下錯誤：
[root@backup-system cpu]# docker run -ti --name hkp_ubuntu --cpuset-cpus=0-3 ubuntu bash
docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:326: applying cgroup configuration for process caused: failed to write "0-3\n" to "/sys/fs/cgroup/cpuset/docker/cpuset.cpus": write /sys/fs/cgroup/cpuset/docker/cpuset.cpus: invalid argument: unknown.
登入後複製
這個錯誤是因為該cgroup的cpu正在被其它cgroup使用，所以不能設定獨佔。
因此需要先檢查並調整各個cgroup的cpuset.cpus，確保當前cgroup所用的cpu的確只分配給它了，那麼此時就可以設定cpu_exclusive獨佔了。
目前的具體原因是做實驗在/sys/fs/cgroup/cpuset/新建了container目錄，並把container/cpuset.cpus 設定為了0-3
[root@backup-system docker]# cat /sys/fs/cgroup/cpuset/container/cpuset.cpus
0-3
登入後複製
解決方法：
將/sys/fs/cgroup/cpuset/container/cpuset.cpus設為空後，上述問題解決。
推薦學習：《docker影片教學》
以上是啟動docker報錯如何解決的詳細內容。更多資訊請關注PHP中文網其他相關文章！
