Sometimes, after an improper shutdown, docker might fail to (re)start and report a network conflict due do multiple bridge networks having the same name.
INFO[...] Starting up INFO[...] [graphdriver] using prior storage driver: overlay2 INFO[...] Loading containers: start. INFO[...] 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[...] stopping event stream following graceful shutdown error="<nil>" module=libcontainerd namespace=moby INFO[...] stopping event stream following graceful shutdown error="context canceled" module=libcontainerd namespace=plugins.moby failed to start daemon: Error initializing network controller: error creating default "bridge" network: cannot create network 753fe3500325b9c1269007561303146077acc7ca455c5dad23f03592dc98f165 (docker0): conflicts with network 48854b5411c5bc123580d1b4eaab5e046d311cbbf99e777e2ade00788429479e (docker0): networks have same bridge name
This happens because of leftover files in docker’s configuration. One workaround solution for quickly getting things up and running again is to delete the existing network configuration and have docker generate a new one on startup. To accomplish this, navigate into /var/lib/docker and remove (delete or rename) the network/ subfolder.
cd /var/lib/docker/ mv network/ network-disabled
Then attempt to test start docker interactively:
dockerd
If it starts successfully, you can quit the interactive session and start the service:
service docker start
