Unit is not loaded properly: Invalid argument. See system logs and ‘systemctl status docker.service

docker启动异常
查阅了网络资料很多都说删除/etc/systemd/system/docker.service 该文件 进行重新安装docker

但是我使用了另一种方式
1.备份docker.service文件
2.使用一下的默认内容覆盖docker.service文件

[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
BindsTo=containerd.service
After=network-online.target firewalld.service containerd.service
Wants=network-online.target
Requires=docker.socket

[Service]
Type=notify
# the default is not to use systemd for cgroups because the delegate issues still
# exists and systemd currently does not support the cgroup feature set required
# for containers run by docker
ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
ExecReload=/bin/kill -s HUP $MAINPID
TimeoutSec=0
RestartSec=2
Restart=always

# Note that StartLimit* options were moved from "Service" to "Unit" in systemd 229.
# Both the old, and new location are accepted by systemd 229 and up, so using the old location
# to make them work for either version of systemd.
StartLimitBurst=3

# Note that StartLimitInterval was renamed to StartLimitIntervalSec in systemd 230.
# Both the old, and new name are accepted by systemd 230 and up, so using the old name to make
# this option work for either version of systemd.
StartLimitInterval=60s

# Having non-zero Limit*s causes performance problems due to accounting overhead
# in the kernel. We recommend using cgroups to do container-local accounting.
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity

# Comment TasksMax if your systemd version does not support it.
# Only systemd 226 and above support this option.
TasksMax=infinity

# set delegate yes so that systemd does not reset the cgroups of docker containers
Delegate=yes

# kill only the docker process, not all processes in the cgroup
KillMode=process

[Install]
WantedBy=multi-user.target

3.输入命令测试

systemctl daemon-reload && systemctl restart docker

问题得到解决！
在可以启动的文件基础上 ， 将原备份文件中的配置 手动添加到 当前的docker.service 文件中， 如果启动失败，那就可以明确的定位到 是添加的配置错误了 ，解决起来也很容易了
不需要删除文件 卸载重装了 费时费力
[原创]