I think you forgot to share the details in the template that I assume you used.
system prune should not rmove running containers, only unused images, but we can’t tel if it is a bug or using the wrong Docker without knowing what you use. Regarding growing docker data root, usually large amount of logs sent to the standard output or writing files to the container filesystem can fill up the space. Especially when the container is failing and restarting.
Let me share the template that includes the questions that help us to understand the issue:
We usually need the following information to understand the issue:
What platform are you using? Windows, Linux or macOS? Which version of the operating systems? In case of Linux, which distribution?
How did you install Docker? Sharing the platform almost answers it, but only almost. Direct links to the followed guide can be useful.
On debian based Linux, the following commands can give us some idea and recognize incorrectly installed Docker:
docker info
docker version
Review the output before sharing and remove confidential data if any appears (public IP for example)
docker.io is supported by the maintainers of the Linux distribution, not Docker. The officially supported and recomended Docker engine is Docker CE as described here.
It starts with deleting docker.io
Can you install that? If not, we can focus on the space usage, which is not likely to be different in the two engines, but if you found a bug in docker.io it would be better if you could reproduce it with Docker CE before reporting it to Docker. There are also newer Docker versions. 28.5.2 is the latest of v28 and there is also v29, so if there was an actual bug that removed containers, it is likely that it was already fixe din newer versions.