Running systemctl daemon-reload and systemctl restart docker resulted in the loss of container metadata

General
3

First of all, thank you for your reply. I’m sorry, this is my first time posting in the Docker community, and I’m not very familiar with the rules. Let me clarify the issue I encountered and the steps I took. The problem occurred after performing the following steps:

  1. Modified the daemon.json file to:
{
    "runtimes": {
        "nvidia": {
            "path": "nvidia-container-runtime",
            "runtimeArgs": []
        }
    },
    "registry-mirrors": [
        "https://hub.fast360.xyz",
        "https://hub.rat.dev",
        "https://hub.littlediary.cn",
        "https://docker.kejilion.pro",
        "https://dockerpull.cn",
        "https://docker-0.unsee.tech",
        "https://docker.tbedu.top",
        "https://docker.1panelproxy.com"
    ]
}
  1. Used systemctl daemon-reload and systemctl restart docker to restart, but found that docker ps -a and docker images showed no information.

After repeatedly trying, I remounted the disk but still couldn’t see anything. I then rebooted the server, and docker ps -a still showed no information.

The Docker directory is mounted on the disk /dev/nvme0n1, which has 3.5T capacity, 2.5T used, and 1.1T available (72% usage) at /var/lib/docker. I’ve been using the same one, and I’m sure I could see the container information before the issue occurred.

If this situation isn’t data loss, how can Docker recognize the container information?