SIGBUS Error when starting containerd

Docker Engine General
,
1

Hi,
I’ve been running my home server for quite a while now, and everything worked fine until there was a power outage last night. My server got shutdown instantly because of that, and now I can’t run docker.

After a bit of investigation, I found that docker couldn’t start because it couldn’t reach containerd, so I used journalctl -xeu containerd.service to find out more about containerd, and I found this error which I cannot fix, even after reinstalling docker:

unexpected fault address 0x##########
fatal error: fault
[signal SIGBUS: bus error code=0x2 addr=0x########## pc=0x##########]

(I replaced the address with ### but I don’t think it’s relevant what address is displayed)

Would anyone be able to help with this? I couldn’t find anything online.

2

Not sure about this, but if it happened after a power outage, it is possible that the filesystem was corrupted. Since containerd is installed as a dependency, even if you delete docker-ce, the containerd.io package can still be there.

If any metadata file was partially written under /var/lib/containerd, I can imagine fatal error.

If you could not solve it yet, can you share more about the host OS, Docker version and containerd version?