Docker got corrupted? after forced shutdown

If a simple re-install didn't do it, you may need to actually uninstall/purge, autoclean, and then re-install. I say this because I had a glitch one time that required doing that to fix it.

1) apt-get remove docker* --purge

2) apt-get autoclean

3) then reinstall docker via the GUI.

This should:

1) remove docker and purge any config files by adding the --purge to the remove command (or by replacing "remove" with purge)

2) remove any dependencies that are not needed by something else in case the problem is with a docker dependency.

3) reinstall will put it all back together.

I haven't tried this using the compose plugin as my docker compose manager (the compose plugin didn't exist at the time), but in theory, because the remove is happing via straight apt-get at the cli and not re-writing the OMV database/xml, all the compose files should be retained in there. To be save though, you should make sure you have copies of your compose files just in case. Once docker is working again, all your containers should just "magically" work again, but if not, you can copy paste the compose files back into the GUI.

The error is saying the docker service failed to start but not why. You need to do as the error says and post the info. It may tell why.

See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.

I am by no means an expert in log parsing, but I do see 2 errors that might point to the problem.

Sep 04 19:18:31 NAS dockerd[3658]: failed to start daemon: Error initializing network controller: error creating default "bridge" network: canno>

Process: 3819 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)

It looks to me like docker is unable to create the basic docker bridge network it needs, and likely the other two default ones it creates (host and none) and containerd may also having start problems. Docker and containerd go hand in hand.

Might want to do a systemctl status containerd to check it's state out of curiosity

My next step would be to do a more complete uninstall/re-install cycle tackling containerd as well

1) apt-get remove docker* --purge

2) apt-get remove containerd* --purge

3) remove the the /etc/containerd directory and the /etc/docker directory if they still exist after the purge, as they hold config files

4) apt-get autoclean

5 omv-aptclean

6) then reinstall docker via the GUI.

On a Quick Look (sorry at work at the moment can’t look in real depth) I’m not seeing any kind of decernable error coded in there that might point to the reason for the failure.

Does systemctl status containerd show containerd running?

Just had a chance to look closer. Still not seeing anything that points to a problem. I think I will have to defer to someone who is better versed in this. Perhaps ryecoaaron can help better, as he is the one that makes the omv-extras plugins.