The mounted disk didn’t show any issues, and I only entered two commands. Has anyone encountered a similar problem? Please help me. :persevering_face: [image]

Please, use </> button to share codes, terminal outputs, error messages instead of sharing screenshots. That helps others to search for similar issues and us to read it more easily and quote parts of the message so we can help you more quickly. You can find a complete guide in the following post: Ho…

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: Modified the daemon.json file …

Please, don’t create new topics for the same question. I assume it was not intentional, but I deleted one topic and merged another to this topic because you shared more information in it. The spamfilter can block posts and remains hidden until a moderator accepts it, but if you send the same post in…

Thank you again for your response. Here is the information I have gathered: I also believe the issue occurred before I restarted the Docker service, but I couldn’t find any logs to support this view. root@dbcloud:~# docker info Client: Docker Engine - Community Version: 26.1.0 Context: defa…

So nothing seems to be wrong, but I start to understand your previous posts like: [image] luowenpeng: 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. So you meant you always used this dis…

Thank you for your response. The repositories.json file is empty, and it seems likely that the data cannot be recovered. Fortunately, the data in the overlay2 directory is still intact, so I can transfer the important files, though it might be a bit troublesome. Thank you very much!

I tested removing the content of the repository json and restarting Docker. It would not even start. Even if I add {} as content, the images are still listed in the output of docker image ls, except there are no tags. Which is actually understandable as that file just maps the tags to IDs. So if you…

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

General

system (system) Closed May 30, 2025, 9:14pm 10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Docker images and container lost not visible WARNING:root:could not open file '/etc/apt/sources.list.d/docker.list' Docker Hub docker	16	4208	June 15, 2022
Unable to restart the container when the data of data-root is lost General docker	1	1076	March 7, 2019
Docker not loading containers from filesystem after reboot General	3	2288	June 26, 2023
Daemon restart removing layers, breaking images, cant start containers General docker	0	1256	April 12, 2021
Systemctl daemon-reload reset docker container cgroup General docker	5	106	December 20, 2025

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

Related topics