Needs a new backup system

Description

The backup system in docker is the worst most garbage backup system I've ever seen in my 25 years of living and in any software. I spent over 5 ****** hours trying to recover MY data, have about 11+ years of experience in IT and many years with self-hosted apps in docker can't because the backup system in Docker is unusable.

Basically you store anything in a docker volume, just assume it can never be reached again except for that exact computer. Someone spends hours of their life self-hosting something they need for day to day work and their computer dies? Screwed out of all that date, If this were an enterprise that needs uptime it would be billions of dollars lost over bad programming.

I tried copying /var/lib/docker but that doesn't work for some magic reason. I did exact copy with rsync, exact permissions and even factoring in ACLs and any minute little thing, nope. Don't work. How is this even possible? How can a program just not at all recognize the exact data on another computer unless it's deliberately coded to frustrate the end user.

Here is how it should work:

docker backup --all

Then it just makes a zip file, then to restore:

docker restore --all

Whoever made this system needs to fire them immediately they are an active hindrance to your project. Multi billion dollar enterprises are losing time and money on this joke of a system and they should be fired immediately.

Reproduce

.

Expected behavior

No response

docker version

.

docker info

.

Additional Info

No response

The proposal is for new docker backup --all and docker restore --all commands in the Docker CLI. Start by locating the CLI entry points and existing volume or archive handling, then define portability and recovery requirements; done should include a usable backup and restore flow, with tests covering the supported data.