GVKun编程网logo

解决 docker 报错: Error starting daemon: error initializing graphdriver: backing file system is unsup...

8

这篇文章主要围绕解决docker报错:Errorstartingdaemon:errorinitializinggraphdriver:backingfilesystemisunsup...展开,旨在

这篇文章主要围绕解决 docker 报错: Error starting daemon: error initializing graphdriver: backing file system is unsup...展开,旨在为您提供一份详细的参考资料。我们将全面介绍解决 docker 报错: Error starting daemon: error initializing graphdriver: backing file system is unsup...,同时也会为您带来Centos 使用Systemctl报Error getting authority: Error initializing authority: Error calling StartServ...、Docker - 解决 Error response from daemon: driver failed programming external connectivity on endpoint tomcat9999、Docker - 解决同步容器与主机时间报错:Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/usr/share/zoneinfo/UTC" -> "../usr/share/zoneinfo/Asia/Shanghai"、docker daemon 端口冲Failed to start Docker Application Container Engine. -- Subject: Unit docker.servic的实用方法。

本文目录一览:

解决 docker 报错: Error starting daemon: error initializing graphdriver: backing file system is unsup...

解决 docker 报错: Error starting daemon: error initializing graphdriver: backing file system is unsup...

CentOS 7.5 x64下

sudo yum install docker -y 

systemctl enable docker

systemctl start docker

发现启动失败

journalctl -xe

查询获得报错


Jan 11 22:49:16 localhost.localdomain dockerd-current[29403]: time="2019-01-11T22:49:16.686305029+08:00" level=info msg="libcontainerd: new containerd process, pid: 29410"
Jan 11 22:49:17 localhost.localdomain dockerd-current[29403]: time="2019-01-11T22:49:17.696062387+08:00" level=error msg="''overlay2'' requires kernel 4.7 to use on btrfs"
Jan 11 22:49:17 localhost.localdomain dockerd-current[29403]: Error starting daemon: error initializing graphdriver: backing file system is unsupported for this graph driver


docker.service: main process exited, code=exited, status=1/FAILURE

Failed to start Docker Application Container Engine.

 

然后搜索了一番,暂时没找到。 然后就自己研究一下。

cat /etc/systemd/system/multi-user.target.wants/docker.service


[Unit]
Description=Docker Application Container Engine
Documentation=http://docs.docker.com
After=network.target
Wants=docker-storage-setup.service
Requires=docker-cleanup.timer

[Service]
Type=notify
NotifyAccess=main
EnvironmentFile=-/run/containers/registries.conf
EnvironmentFile=-/etc/sysconfig/docker
EnvironmentFile=-/etc/sysconfig/docker-storage
EnvironmentFile=-/etc/sysconfig/docker-network
Environment=GOTRACEBACK=crash
Environment=DOCKER_HTTP_HOST_COMPAT=1
Environment=PATH=/usr/libexec/docker:/usr/bin:/usr/sbin
ExecStart=/usr/bin/dockerd-current \
--add-runtime docker-runc=/usr/libexec/docker/docker-runc-current \
--default-runtime=docker-runc \
--exec-opt native.cgroupdriver=systemd \
--userland-proxy-path=/usr/libexec/docker/docker-proxy-current \
--init-path=/usr/libexec/docker/docker-init-current \
--seccomp-profile=/etc/docker/seccomp.json \
$OPTIONS \
$DOCKER_STORAGE_OPTIONS \
$DOCKER_NETWORK_OPTIONS \
$ADD_REGISTRY \
$BLOCK_REGISTRY \
$INSECURE_REGISTRY \
$REGISTRIES
ExecReload=/bin/kill -s HUP $MAINPID
LimitNOFILE=1048576
LimitNPROC=1048576
LimitCORE=infinity
TimeoutStartSec=0
Restart=on-abnormal
KillMode=process

[Install]
WantedBy=multi-user.target

cat /etc/sysconfig/docker-storage

DOCKER_STORAGE_OPTIONS="--storage-driver overlay2 "

尝试执行dockerd 命令,结果运行成功,提示:

dockerd
INFO[0000] libcontainerd: new containerd process, pid: 29626 
WARN[0000] containerd: low RLIMIT_NOFILE changing to max  current=1024 max=4096
INFO[0001] [graphdriver] using prior storage driver: btrfs 
INFO[0001] Graph migration to content-addressability took 0.00 seconds 
INFO[0001] Loading containers: start.                   
INFO[0001] Firewalld running: false                     
INFO[0001] Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address 
INFO[0001] Loading containers: done.                    
WARN[0001] failed to retrieve docker-runc version: exec: "docker-runc": executable file not found in $PATH 
WARN[0001] failed to retrieve docker-init version       
INFO[0001] Daemon has completed initialization          
INFO[0001] Docker daemon                                 commit="07f3374/1.13.1" graphdriver=btrfs version=1.13.1
INFO[0001] API listen on /var/run/docker.sock

发现了关键字:   graphdriver=btrfs 以及之前的报错有提示:  error msg="''overlay2'' requires kernel 4.7 to use on btrfs"

所以尝试修改 /etc/sysconfig/docker-storage 为:
DOCKER_STORAGE_OPTIONS="--storage-driver btrfs "

重新启动docker:

systemctl start docker

启动成功.问题解决!

下面开始 docker 学习.

 



Centos 使用Systemctl报Error getting authority: Error initializing authority: Error calling StartServ...

Centos 使用Systemctl报Error getting authority: Error initializing authority: Error calling StartServ...

[root@iZbp1he0bdge2g92l9fjnxZ ~]# systemctl  restart  zabbix-agent
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
Failed to restart zabbix-agent.service: Connection timed out
See system logs and ''systemctl status zabbix-agent.service'' for details.

在使用centos7.4 安装服务的时候报错:

  在启动zabbix时候报错: 

Centos 使用Systemctl报Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)

Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)

解决方案:

ps -ef |grep polkit

再安装:
 pyum reinstall polkit

再重启
reboot

 

 

Docker - 解决 Error response from daemon: driver failed programming external connectivity on endpoint tomcat9999

Docker - 解决 Error response from daemon: driver failed programming external connectivity on endpoint tomcat9999

问题背景

执行 docker start tomcat 报以下的错误

Error response from daemon: driver Failed programming external connectivity on endpoint tomcat9999 (f24431f0da474edbe79ba136b19079df3dcae89a4f688abe74cd0b993856a670):  (iptables Failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 8080 -j DNAT -

 

解决办法

docker服务启动时定义的自定义链DOCKER被清除,重启即可

systemctl restart docker

 

总结

以上是小编为你收集整理的Docker - 解决 Error response from daemon: driver failed programming external connectivity on endpoint tomcat9999全部内容。

如果觉得小编网站内容还不错,欢迎将小编网站推荐给好友。

"../usr/share/zoneinfo/Asia/Shanghai"" alt="Docker - 解决同步容器与主机时间报错:Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/usr/share/zoneinfo/UTC" -> "../usr/share/zoneinfo/Asia/Shanghai"">

问题背景

  • 这里讲解了如何同步容器和主机的时间:https://www.cnblogs.com/poloyy/p/13967532.html
  • 其中使用方法二 docker cp /etc/localtime [容器ID或名字]:/etc/localtime 报错了

 

解决方案

docker cp /usr/share/zoneinfo/Asia/Shanghai gitlab:/etc/localtime

 

重启容器

docker restart gitlab

 

进入容器进行验证

docker exec -it gitlab bash

 

docker daemon 端口冲Failed to start Docker Application Container Engine. -- Subject: Unit docker.servic

docker daemon 端口冲Failed to start Docker Application Container Engine. -- Subject: Unit docker.servic

Failed to start Docker Application Container Engine.
– Subject: Unit docker.service has Failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit docker.service has Failed.

– The result is Failed.


原因有很多
我的是这样的:
我stop 了其它的容器,新建了一个容器,用了一端口,而没注意到这个端口与其它容器端口是一样的,

后来,我要修改端口映射,去container目录下改hostconfig 之前 ,停止了docker 服务。

改了之后,启动服务。
由于之前的容器,是restart=always 。所以启动的时候,那两个冲突容器也启动了。所以失败。

解决:
备份,》删除 。
logs没有什么信息systemctl status docker journalctl -xe也没有什么信息

docker ps 卡住,???好像是启动了,但。。。
使用dockerd

Failed to start daemon: pid file found, ensure docker is not running or delete /var/run/docker.pid

有进程了?》删除 kill -9 pid
再dockerd
Error (Unable to complete atomic operation, key modified) deleting object [endpoint d14ea1a4
无法原子操作。
docker ps有东西了。
start 冲突的容器。出现了bind: address already in use。。结下来,要么删除容器,要么,再去改hostconifg来一遍。

今天关于解决 docker 报错: Error starting daemon: error initializing graphdriver: backing file system is unsup...的讲解已经结束,谢谢您的阅读,如果想了解更多关于Centos 使用Systemctl报Error getting authority: Error initializing authority: Error calling StartServ...、Docker - 解决 Error response from daemon: driver failed programming external connectivity on endpoint tomcat9999、Docker - 解决同步容器与主机时间报错:Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/usr/share/zoneinfo/UTC" -> "../usr/share/zoneinfo/Asia/Shanghai"、docker daemon 端口冲Failed to start Docker Application Container Engine. -- Subject: Unit docker.servic的相关知识,请在本站搜索。

本文标签: