在停止docker之后,它拒绝重新启动。它抱怨另一个名为docker0的桥已经存在:
level=warning msg="devmapper: Base device already exists and has filesystem xfs on it. User specified filesystem will be ignored."
level=info msg="[graphdriver] using prior storage driver \"devicemapper\""
level=info msg="Graph migration to content-addressability took 0.00 seconds"
level=info msg="Firewalld running: false"
level=info msg="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"
level=fatal msg="Error starting daemon: Error initializing network controller: Error creating default \"bridge\" network: cannot create network fa74b0de61a17ffe68b9a8f7c1cd698692fb56f6151a7898d66a30350ca0085f (docker0): conflicts with network bb9e0aab24dd1f4e61f8e7a46d4801875ade36af79d7d868c9a6ddf55070d4d7 (docker0): networks have same bridge name"
docker.service: Main process exited, code=exited, status=1/FAILURE
Failed to start Docker Application Container Engine.
docker.service: Unit entered failed state.
docker.service: Failed with result 'exit-code'.使用ip link del docker0删除网桥,然后启动docker会导致使用另一个id得到相同的结果。
发布于 2016-11-10 17:57:32
问题似乎出在/var/docker/network/上。存储了许多套接字,这些套接字通过桥的旧id引用桥。要解决这个问题,你可以删除所有的套接字,删除接口,然后启动docker ,但是你所有的容器都会拒绝工作,因为它们的套接字都没有了。在我的例子中,我并不关心我的无状态容器,所以这解决了这个问题:
ip link del docker0
rm -rf /var/docker/network/*
mkdir /var/docker/network/files
systemctl start docker
# delete all containers
docker ps -a | cut -d' ' -f 1 | xargs -n 1 echo docker rm -f
# recreate all containers发布于 2017-03-16 22:18:48
对我来说,我降级了我的操作系统(在本例中是Centos原子主机),并遇到了这个错误消息。更老的Centos原子的对接器是1.9.1。在运行降级之前,我没有任何运行的docker容器或图像。
我只是简单地运行了下面的代码,又很高兴了:
sudo rm -rf /var/lib/docker/network
sudo systemctl start dockerhttps://stackoverflow.com/questions/40524602
复制相似问题