docker - Error creating default \"bridge\" network: cannot create network (docker0): conflicts with network (docker0): networks have same bridge name -


after stopping docker refused start again. complaint bridge called docker0 exists:

level=warning msg="devmapper: base device exists , has filesystem xfs on it. user specified filesystem  ignored." level=info msg="[graphdriver] using prior storage driver \"devicemapper\"" level=info msg="graph migration content-addressability took 0.00 seconds" level=info msg="firewalld running: false" level=info msg="default bridge (docker0) assigned ip address 172.17.0.0/16. daemon option --bip can used set preferred ip address" level=fatal msg="error starting daemon: error initializing network controller: error creating default \"bridge\" network: cannot create network fa74b0de61a17ffe68b9a8f7c1cd698692fb56f6151a7898d66a30350ca0085f (docker0): conflicts network bb9e0aab24dd1f4e61f8e7a46d4801875ade36af79d7d868c9a6ddf55070d4d7 (docker0): networks have same bridge name" docker.service: main process exited, code=exited, status=1/failure failed start docker application container engine. docker.service: unit entered failed state. docker.service: failed result 'exit-code'. 

deleting bridge ip link del docker0 , starting docker leads same result id.

for me downgraded os (centos atomic host in case) , came across error message. docker of older centos atomic 1.9.1. did not have running docker containers or images pulled before running downgrade.

i ran below , docker happy again:

sudo rm -rf /var/lib/docker/network sudo systemctl start docker 

more info.


Comments

Popular posts from this blog

asynchronous - C# WinSCP .NET assembly: How to upload multiple files asynchronously -

aws api gateway - SerializationException in posting new Records via Dynamodb Proxy Service in API -

asp.net - Problems sending emails from forum -