systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Thu 2023-03-02 18:40:16 CST; 2min 54s ago
Docs: https://docs.docker.com
Process: 2555 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 2555 (code=exited, status=1/FAILURE)
Mar 02 18:40:13 k8s-master systemd[1]: Unit docker.service entered failed state.
Mar 02 18:40:13 k8s-master systemd[1]: docker.service failed.
Mar 02 18:40:16 k8s-master systemd[1]: docker.service holdoff time over, scheduling restart.
Mar 02 18:40:16 k8s-master systemd[1]: Stopped Docker Application Container Engine.
Mar 02 18:40:16 k8s-master systemd[1]: start request repeated too quickly for docker.service
Mar 02 18:40:16 k8s-master systemd[1]: Failed to start Docker Application Container Engine.
Mar 02 18:40:16 k8s-master systemd[1]: Unit docker.service entered failed state.
Mar 02 18:40:16 k8s-master systemd[1]: docker.service failed.q全网各种查找“docker.service: Service hold-off time over, scheduling restart”，各种说法
有说/etc/docker/daemon.json 格式不对
有说/etc/docker/daemon.json 改为/etc/docker/daemon.conf，都试了没用
最后看到一个大佬说，重启systemctl restart docker.service 后，
马上按systemctl status docker.service 或 journalctl -xe,可以看到更详细的报错;
[root@xxx docker]# systemctl restart docker.service
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
[root@xxx docker]# journalctl -xe
Mar 02 18:44:33 k8s-master dockerd[2648]: time="2023-03-02T18:44:33.921429349+08:00" level=info msg="scheme \
Mar 02 18:44:33 k8s-master dockerd[2648]: time="2023-03-02T18:44:33.921448526+08:00" level=info msg="ccResolv
Mar 02 18:44:33 k8s-master dockerd[2648]: time="2023-03-02T18:44:33.921509775+08:00" level=info msg="ClientCo
Mar 02 18:44:33 k8s-master kernel: XFS (sda3): Metadata corruption detected at xfs_inode_buf_verify+0x14d/0x1
Mar 02 18:44:33 k8s-master kernel: XFS (sda3): Unmount and run xfs_repair
Mar 02 18:44:33 k8s-master kernel: XFS (sda3): First 128 bytes of corrupted metadata buffer:
Mar 02 18:44:33 k8s-master kernel: ffff9094dede8000: 0b 68 78 d8 4b 00 ff 15 04 35 4a 00 ff 75 14 e8 .hx.K..
Mar 02 18:44:33 k8s-master kernel: ffff9094dede8010: 7c 02 00 00 ff 47 04 8b d8 8b 4d 10 89 4b 04 8b |....G.
Mar 02 18:44:33 k8s-master kernel: ffff9094dede8020: 07 3b c8 75 0b 89 58 04 8b 07 89 18 8b 07 eb 1c .;.u..X
Mar 02 18:44:33 k8s-master kernel: ffff9094dede8030: 80 7d 0c 00 74 0c 89 19 8b 07 3b 08 75 11 89 18 .}..t..
Mar 02 18:44:33 k8s-master kernel: ffff9094dede8040: eb 0d 89 59 08 8b 07 3b 48 08 75 03 89 58 08 8b ...Y...
Mar 02 18:44:33 k8s-master kernel: ffff9094dede8050: 43 04 8b f3 80 78 0c 00 0f 85 0c 01 00 00 66 90 C....x.
Mar 02 18:44:33 k8s-master kernel: ffff9094dede8060: 8b 46 04 8b 50 04 8b 0a 3b c1 75 74 8b 4a 08 80 .F..P..
Mar 02 18:44:33 k8s-master kernel: ffff9094dede8070: 79 0c 00 74 71 3b 70 08 75 0a 8b f0 8b cf 56 e8 y..tq;p
Mar 02 18:44:33 k8s-master kernel: XFS (sda3): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x4b18
Mar 02 18:44:33 k8s-master kernel: XFS (sda3): xfs_imap_to_bp: xfs_trans_read_buf() returned error -117.
Mar 02 18:44:33 k8s-master dockerd[2648]: failed to start daemon: lstat /var/lib/docker/image/overlay2/layerd
Mar 02 18:44:33 k8s-master systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Mar 02 18:44:33 k8s-master systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed终于发现问题所在了，我的是在vmware虚拟机 跑的docker，上次异常关机重启了，分区损坏了，-_-||
参考解决办法：
1：启动虚拟机E进入单用户模式
2：在linux16开头的哪一行后面添加rd.break，ctrl+x进入救援模式
3：执行umount /dev/sda3
执行xfs_repair -L /dev/sda3
如无报错，重启虚拟机，检查docker已经正常
以下是参考链接：
docker 启动失败，查看更详细的报错
https://blog.csdn.net/zengyaowu1988/article/details/108400029
重启虚拟机异常：unmount and run xfs_repair
https://blog.csdn.net/qq_35022803/article/details/109287086