Docker Couldn't create socket: [111] Connection refused

[nivagator]

After a reboot, the Docker will not start. 

 

The error on the GUI is:

Docker Service failed to start.

Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 712
Couldn't create socket: [111] Connection refused
Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 898

 

docker.txt log shows:

failed to start daemon: Error initializing network controller: could not delete the default bridge network: network bridge id 96d4f72b55fb181998c3639f0946f75e3ced5a47a4e76b9af0218118c109432a has active endpoints

 

Diagnostics attached. Any help to resolve would be greatly appreciated. 

galaxy-diagnostics-20230412-2048.zip

[kentb]

I've just had the same issue. Docker refused to start. I changed th eimage file to an actual folder to help diagnose it, and this error occurred.

[nivagator]

Unfortunately, I wasn't able to find a solution to keep my existing containers. I wiped the docker image entirely and started over deploying them all from the saved templates. It worked ok and only required a bit of manual tweaking to get it all back. The biggest challenge was the downtime. I can't prove it but I think it was something to do with the btrfs cache I had spanning two SSDs. After the wipe, I started over with a single, XFS cache and more robust backups.